Hello Tim, Considering that there’s no evidence of anyone using the feature, that it doesn’t work well in all circumstances, that we have an alternative which works better and has no downsides (considering the new policy on dependencies), I think that’s reasonable.
I’m afraid we’ll get a couple complaints a few months after we’ll drop security support for 1.8, not during the 1.11 alpha period… But that doesn’t change my arguments. If we get feedback during 1.11 alpha then we’ll have to reconsider. (Disclaimer — I’m more tolerant of backwards-incompatible changes than many other committers.) -- Aymeric. > On 24 Oct 2016, at 22:51, Tim Graham <timogra...@gmail.com> wrote: > > I asked on django-users [0] if anyone is using settings.TIME_ZONE=None and > didn't get any responses. Does it seem okay to drop that for now and react if > we get any complaints about its removal? > > [0] https://groups.google.com/d/topic/django-users/CxAiS6PXs3U/discussion > <https://groups.google.com/d/topic/django-users/CxAiS6PXs3U/discussion> > > On Wednesday, October 12, 2016 at 3:12:44 PM UTC-4, Tim Graham wrote: > Would you be comfortable recommending that package for anyone who needs the > autodetection? This seems to work: > > from tzlocal import get_localzone > TIME_ZONE = get_localzone().zone > > What would change compared to the behavior of TIME_ZONE=None is that Django > will set os.environ['TZ'] (except on Windows). I don't really understand the > use case where doing that may have been a problem [0]. > > [0] https://code.djangoproject.com/ticket/1480 > <https://code.djangoproject.com/ticket/1480> > On Wednesday, October 12, 2016 at 12:58:19 PM UTC-4, Aymeric Augustin wrote: > > On 12 Oct 2016, at 18:22, Tim Graham <timog...@gmail.com <>> wrote: > > > > is there some other approach we could take? > > To obtain the pytz timezone for the local time, you’d need something like: > https://github.com/regebro/tzlocal <https://github.com/regebro/tzlocal> > > It isn’t exactly straightforward… This approach seems sub-optimal. > > -- > 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 > <mailto:django-developers+unsubscr...@googlegroups.com>. > To post to this group, send email to django-developers@googlegroups.com > <mailto:django-developers@googlegroups.com>. > Visit this group at https://groups.google.com/group/django-developers > <https://groups.google.com/group/django-developers>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/django-developers/f83d112d-d2c6-4201-91ad-80578f23df0d%40googlegroups.com > > <https://groups.google.com/d/msgid/django-developers/f83d112d-d2c6-4201-91ad-80578f23df0d%40googlegroups.com?utm_medium=email&utm_source=footer>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- 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/7747B0D4-153D-4B6C-9F8F-2517E85BAFD9%40polytechnique.org. For more options, visit https://groups.google.com/d/optout.
