#11385: DateTimeField doesn't accept ISO 8601 formatted date string
-------------------------------------+-------------------------------------
Reporter: jtiai | Owner: nobody
Type: Uncategorized | Status: closed
Component: Database layer | Version: 1.0
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: datetime orm format | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by matthewslaney):
* ui_ux: => 0
* type: => Uncategorized
* severity: => Normal
* easy: => 0
Comment:
Replying to [comment:1 russellm]:
> ISO8601 is a good machine format, but not a particularly nice human
readable format. Form processing is primarily about human-readable input.
>
> If you disagree, the DateTimeField input formats are configurable
(DATETIME_INPUT_FORMATS), so you can add ISO8601 format in your own
projects if you want.
Hi Russell,
I understand your reasoning at the time this was closed for not supporting
the T separator. However, this is not relevant again because of the way
HTML5 provides the new Input Types. By default, using the datetime-local
Input Type results in the format of YYYY-MM-DDTHH:MM. It would definitely
make it nice to allow for that Input Type default to work properly with
DateTimeField.
--
Ticket URL: <https://code.djangoproject.com/ticket/11385#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.5f285ca25953e6ea5bb418c2beb0b9e4%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
