> On 10 Oct 2016, at 21:31, Tim Graham <timogra...@gmail.com> wrote: > > I forgot to mention (and document) that (if I'm following the code correctly) > this change removes support for setting TIME_ZONE=None. According to the > docs, TIME_ZONE=None "causes cause Django to fall back to using the system > timezone. However, this is discouraged when USE_TZ = True > <https://groups.google.com/forum/#std:setting-USE_TZ>, because it makes > conversions between local time and UTC less reliable." Is removing that > option acceptable as a backwards-incompatible change?
I don’t have an opinion on that. I don’t think USE_TZ = None provides a particularly useful behavior. I think it’s best to state the expected value explicitly. Perhaps that option was implemented because someone asked for it? I don’t remember. -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/70E556C2-6CF6-43CF-9763-89EE0C50C2EB%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
