In 1.4, what exactly is the scope of the current timezone? In other words, if I use activate() to set a current timezone, is that global? Or does it only apply to the current request (and not persist across requests)? Or, some other scope? (I looked at the source<https://code.djangoproject.com/browser/django/trunk/django/utils/timezone.py#L155>and it appears that it might apply to the current *thread,* but I'm not familiar with how Django uses threads, so I don't know how that affects the answer.)
I've read the documentation here<https://docs.djangoproject.com/en/dev/topics/i18n/timezones/#default-current-time-zone>, and it doesn't really state the scope, as far as I can tell. However, the suggestion to create middleware to handle it is interesting; is this the recommended way to deal with timezones when serving users with a variety of preferred timezones? -- You received this message because you are subscribed to the Google Groups "Django users" group. To view this discussion on the web visit https://groups.google.com/d/msg/django-users/-/C0VoNHVyuxcJ. To post to this group, send email to django-users@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
