On 1 mai 2012, at 19:28, Yo-Yo Ma wrote: > This is because the context manager returns control after dispatch is called, > but the lazy response isn't rendered to a string until later on
Hello, This behavior isn't specific to `timezone.override`. It would also happen with other context managers such as `translation.override`. It's a consequence of using `TemplateResponse`, whose goal is precisely to postpone rendering until the response middleware have run. To set the timezone globally, the docs recommend using `timezone.activate/deactivate` in a middleware (as in `LocaleMiddleware`). Best regards, -- Aymeric. -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
