#13560: SplitDateTimeField(localize=True) fails as value gets converted to
string
------------------------------------------------------------+---------------
Reporter: David Danier <david.dan...@team23.de> | Owner:
nobody
Status: new | Milestone:
Component: Uncategorized | Version:
1.2
Resolution: | Keywords:
localization, SplitDateTimeField, regression
Stage: Unreviewed | Has_patch: 0
Needs_docs: 0 | Needs_tests: 0
Needs_better_patch: 0 |
------------------------------------------------------------+---------------
Changes (by just an idea):
* needs_better_patch: => 0
* needs_tests: => 0
* needs_docs: => 0
Comment:
perhaps it would be best to move localization into the widget at all,
because l10n should not change the state of the internal values (inside
field or boundfield), but only it's representation in the frontend
(widget).
--
Ticket URL: <http://code.djangoproject.com/ticket/13560#comment:1>
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-upda...@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.
