#27304: Django 1.10 onwards broke previous behaviour for models.DateTimeField()
in
Admin
-------------------------------------+-------------------------------------
Reporter: Kegan Gan | Owner: nobody
Type: Bug | Status: new
Component: contrib.admin | Version: 1.10
Severity: Normal | Resolution:
Keywords: model admin | Triage Stage:
datetime formfield_overrides | Unreviewed
AdminDateWidget widget |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Tim Graham):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
Can you [https://docs.djangoproject.com/en/dev/internals/contributing
/triaging-tickets/#bisecting-a-regression bisect] to find where the
behavior changed? Without looking into the details, I'm not immediately
convinced we should treat this as a bug and provide backwards-
compatibility for it, but we'll see.
--
Ticket URL: <https://code.djangoproject.com/ticket/27304#comment:1>
Django <https://code.djangoproject.com/>
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/063.928ccf38d29d65c9d21f8d170b4f4e4b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
