Opened 12 years ago
Closed 12 years ago
#18076 closed Uncategorized (needsinfo)
rfc3339 default support since 1.4 - DateTimeField
| Reported by: | anonymous | Owned by: | nobody |
|---|---|---|---|
| Component: | Forms | Version: | 1.4 |
| Severity: | Normal | Keywords: | time zones rfc3339 |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Since 1.4 claims to support time zones, DateTimeField should support by default rfc3339.
This means that DateTimeField should have some new input_formats by default or this may require using rfc3339.py
from http://henry.precheur.org/projects/rfc3339
Note:
See TracTickets
for help on using tickets.
I fail to see the relationship between time zone support and RFC 3339. From the end user's point of view, this feature doesn't change anything, besides avoiding a class of bugs that could easily bit the programmer.
The design of input formats was centered on formats that humans actually use. Since RFC 3339 isn't a format that average users write spontaneously, I don't see much of a reason to support it in core.
Of course, Django makes it very easy to implement your own form field that supports (and possibly enforces) RFC 3339 if you need it.