#34004: DateTimeField for Forms does not always respect input_formats
--------------------------------+--------------------------------------
Reporter: Emily Hontoria | Owner: nobody
Type: Bug | Status: closed
Component: Forms | Version: 3.1
Severity: Normal | Resolution: invalid
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------+--------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => invalid
Comment:
This was changed in Django 3.1 (see
1487f16f2d29c7aeaf48117d02a1d7bbeafa3d94 and #11385). It's also
[https://docs.djangoproject.com/en/3.2/ref/forms/fields/#datetimefield
documented]:
> ''"The field always accepts strings in ISO 8601 formatted dates or
similar recognized by parse_datetime()"''
> ''Changed in Django 3.1:''
>
> ''Support for ISO 8601 date string parsing (including optional timezone)
was added.''
--
Ticket URL: <https://code.djangoproject.com/ticket/34004#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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/010701832ba8f4f8-38c472a6-5eb5-48fd-8b8b-59ea8871575c-000000%40eu-central-1.amazonses.com.
