#9721: DateTimeField does not support all DEFAULT_DATETIME_INPUT_FORMATS when
passed a list as input
---------------------------------------------+------------------------------
Reporter: uggedal | Owner: nobody
Status: new | Milestone:
Component: Forms | Version: SVN
Resolution: | Keywords: DateTimeFIeld
SplitDateTimeWidget
Stage: Design decision needed | Has_patch: 1
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
---------------------------------------------+------------------------------
Comment (by kmtracey):
Also related: #8898. In general it strikes me that using a
!SplitDateTimeWidget with a !DateTimeField is a wrong approach. We've got
the !SplitDateTimeField to go with the !SplitDateTimeWidget. If there is
some use case that those two together don't support (half of it being
optional) then I think that should be addressed by enhancing them, not
trying to mix together a split widget with a non-split field.
--
Ticket URL: <http://code.djangoproject.com/ticket/9721#comment:4>
Django <http://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 post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to
django-updates+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
