I set up a fresh Django 1.4 project and adapted the middleware described in the docs; I stored the timezone on the user profile of two different users, and logged in as each of them in separate browsers, along with a third completely separate window (so I had three different sessions). It appears that activate() only persists in a given request/response cycle; it didn't bleed through to the unauthenticated window, which wasn't setting its own timezone. So something like the middleware in the docs will work nicely for my uses, I think.
-- 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/-/p7Qfxmu7UeoJ. 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.
