#17262: Refactor the implementations of tzinfo classes
-------------------------------------+-------------------------------------
Reporter: aaugustin | Owner: aaugustin
Type: | Status: new
Cleanup/optimization | Version:
Component: Core | Keywords:
(Other) | Has patch: 0
Severity: Normal | Needs tests: 0
Triage Stage: | Easy pickings: 0
Unreviewed |
Needs documentation: 0 |
Patch needs improvement: 0 |
UI/UX: 0 |
-------------------------------------+-------------------------------------
Since the merge of the time zone support branch, `django.utils.tzinfo` and
`django.utils.timezone` provide subtly different implementations of a
tzinfo subclass representing local time.
The reason is explained at the bottom of [http://groups.google.com/group
/django-developers/msg/c05b469e4335c6cc this message]. In short, the
former is used for display and focuses on robustness; the latter is used
for time zone support and focuses on correctness.
I think `django.utils.tzinfo` should be refactored and merged into
`django.utils.timezone`, but that's probably not doable in a totally
backwards-compatible fashion.
--
Ticket URL: <https://code.djangoproject.com/ticket/17262>
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 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.
