Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  closed
Component:  Forms|  Version:  1.7
 Severity:  Normal   |   Resolution:  fixed
 Keywords:  microseconds | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by Tim Graham ):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:"4dcc6493418c78db07761180bf6265f5b2bbccbf" 4dcc649]:
 {{{
 #!CommitTicketReference repository=""
 revision="4dcc6493418c78db07761180bf6265f5b2bbccbf"
 Fixed #24497 -- Added Widget.supports_microseconds attribute
 }}}

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.5ff416376c88b50525d9de5a4c65dfb9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
-+-
 Reporter:  riklaunim|Owner:  nobody
 Type:  Bug  |   Status:  new
Component:  Forms|  Version:  1.7
 Severity:  Normal   |   Resolution:
 Keywords:  microseconds | Triage Stage:  Ready for
 |  checkin
Has patch:  1|  Needs documentation:  0
  Needs tests:  0|  Patch needs improvement:  0
Easy pickings:  0|UI/UX:  0
-+-
Changes (by timgraham):

 * needs_better_patch:  1 => 0
 * stage:  Accepted => Ready for checkin


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.36ecca91c6eb467c503c228f6c36eb69%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  1
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:  0 => 1


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.eec776f3125541296e6e7a668b961215%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  1 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/4467 PR]

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.241eb1bfbb4bfae2823c99a9e8624fc0%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by wdmgsm):

 It was suggested by bmispelon in this
 [https://github.com/django/django/pull/4373 pull request] to add
 {{{supports_microseconds}}} to the base {{{Widget}}} class so that all
 derived widgets inherit it.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.1a15dac7acd0b70fc7c6a574c3634a57%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by riklaunim):

 Replying to [comment:2 claudep]:
 > It might be a use case for the `supports_microseconds` widget property
 (which needs documentation, by the way).
 >
 > Could you try to subclass `HiddenInput`, set `supports_microseconds`
 class attribute to True for your subclass, and then use that widget in
 your form?

 Depends what should be the default behavior for a ModelForm? Field in a
 model should be tailored to a matching form field and it validation rules.
 If Django must permanently modify DatetTimes for display and alike
 purposes then it should be explicit and consistent with models. If form
 field has supports_microseconds then maybe DateTimeField in a model should
 also have such attribute so that setting timezone.now()/datetime.now()
 etc. won't save with microseconds in the first place?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f3b05493c22eb6257b114ea89feac9f9%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by pkatseas):

 * cc: jiguromusha7@… (added)


--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.2f7761cc91dc51a999c192c4aa31e119%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by bmispelon):

 Documentation issue tracked in #24520.

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.f1ae28ace4fad6cb257b6a3aaf8551fb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by claudep):

 It might be a use case for the `supports_microseconds` widget property
 (which needs documentation, by the way).

 Could you try to subclass `HiddenInput`, set `supports_microseconds` class
 attribute to True for your subclass, and then use that widget in your
 form?

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.9cd3eaa083413f98d40e198183110fca%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #24497: Truncation of microseconds in DateTimeField leads to lookup trouble (was: Form datetime inconsistent handling)

[Django]

#24497: Truncation of microseconds in DateTimeField leads to lookup trouble
--+
 Reporter:  riklaunim |Owner:  nobody
 Type:  Bug   |   Status:  new
Component:  Forms |  Version:  1.7
 Severity:  Normal|   Resolution:
 Keywords:  microseconds  | Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+
Changes (by timgraham):

 * needs_better_patch:   => 0
 * needs_tests:   => 0
 * needs_docs:   => 0
 * type:  Uncategorized => Bug
 * stage:  Unreviewed => Accepted


Comment:

 I guess
 
[https://github.com/django/django/blob/53d11c6821b7b347e0eeefb96168cc1861715a6b/django/forms/forms.py#L618-L622
 this is the offending code].

--
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/067.77edd39abe88ae9d46676c71947e7cee%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.