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. -- 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/59cc28c6-0843-4738-90a6-5afcc52d84b0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
