Other times, the initial callable is handled, but microseconds are
[https://github.com/django/django/blob/698be78d7438aade49d3cac5ea1f9de219d33e42/django/forms/forms.py#L435
not chopped] leading to theoretical false positives that data has changed.
Initial data should be handled more consistently across all cases.
Marking as a bug due to the theoretical edge cases that can produce
unexpected results. Noticed these inconsistencies while working on #27037.
--
Ticket URL: <https://code.djangoproject.com/ticket/27068>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/7097 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/27068#comment:1>
* stage: Unreviewed => Accepted
--
Ticket URL: <https://code.djangoproject.com/ticket/27068#comment:2>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/27068#comment:3>
* status: new => closed
* resolution: => fixed
Comment:
In [changeset:"f5c6d3c8d9fa2158734858fa0a7ac917c384cb97" f5c6d3c8]:
{{{
#!CommitTicketReference repository=""
revision="f5c6d3c8d9fa2158734858fa0a7ac917c384cb97"
Fixed #27068 -- Unified form field initial data retrieval.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/27068#comment:4>