#21074: DateTimeField: Using localized_fields breaks timezone conversion
-------------------------------------+-------------------------------------
Reporter: mattaustin | Owner: aaugustin
Type: Bug | Status: assigned
Component: Forms | Version:
Severity: Normal | 1.6-beta-1
Keywords: timezone | Resolution:
localization forms | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by aaugustin):
* owner: => aaugustin
* status: new => assigned
* severity: Release blocker => Normal
Comment:
Florian rightfully points out that, if the bug can be triggered by setting
`localize=True` on a `DateTimeField`, it isn't new in 1.6. I'll have to
deal with it.
--
Ticket URL: <https://code.djangoproject.com/ticket/21074#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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/068.7732c0d9da8ad1657d8b8757ee132c8f%40djangoproject.com.
For more options, visit https://groups.google.com/groups/opt_out.
