While writing timezone tests for https://github.com/django/django/pull/6243 I ran into some issues where pytz seemed to be required for just about every database and platform combination except postgres on linux. The docs for timezone support (https://docs.djangoproject.com/en/dev/topics/i18n/timezones/) say:
Installing pytz <http://pytz.sourceforge.net/> is highly recommended, but > may not be mandatory depending on your particular database backend, > operating system and time zone. If you encounter an exception querying > dates or times, please try installing it before filing a bug. I tried to find some documentation on the broader internet that would more accurately describe when and for what platforms pytz is actually required for timezone support, but was unable to find anything. I've opened a new ticket https://code.djangoproject.com/ticket/26622 to clarify more explicitly when pytz is required. However, I'm wondering if we should just go all-in on pytz and require it for timezone support. I've not run a Django site with timezone support without pytz, so I'm not sure what exact limitations exist or why you'd want to use timezone support without pytz. I'd be interested in hearing use cases for not requiring pytz if there are any. Explicitly requiring pytz will make test writing a lot easier, and will remove any doubt about whether or not pytz is required for users. Josh -- 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/cb513e96-e75f-462f-a8ca-b5d916ad8eef%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
