Hi Kevin, On 10/09/2016 11:09 AM, Kevin Brown wrote: > I agree with requiring pytz if you have timezone support enabled in > Django, as that cuts out a set of edge cases and likely simplifies the > code base a bit in the long run. And I even agree with forcing it to be > installed with Django if we want to encourage people to use Django with > timezone support by default. > > But I don't see the value in requiring pytz to be installed whenever you > install Django, even if you explicitly disable timezone support. This > means that there is the potential to force pytz to be installed in cases > where it may never be used, and at the moment isn't even required. > > If there was interest in dropping support for using Django without > timezones (so removing USE_TZ = False), then I would understand the push > for making pytz required for everyone.
I made this same argument a while back. The main problem with it is that the default startproject sets USE_TZ = True. That means that with your proposal, the default experience for every new Django dev would be 1. install Django, 2. run startproject, 3. run runserver and get an error that pytz isn't installed. That's not acceptable. Having pytz installed in some cases when it isn't strictly needed is a very small price to pay for a smoother path in the common case. Carl -- 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/f03ff8ad-a71e-ba56-df1e-42f1ef02a41c%40oddbird.net. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: OpenPGP digital signature
