If you include {{ object.some_datetime }} with the America/New_York
timezone activated in a template and get:
April 10, 2013, 10:00 p.m.
Then, take the same object, timezone, etc., and add the |localize filter -
{{ object.some_datetime|localize }} - you'll get:
April 11, 2013, 2:00 a.m.
It seems as if the `localize` filter disables the automatic timezone
converting documented @
https://docs.djangoproject.com/en/dev/topics/i18n/timezones/#time-zone-aware-output-in-templates
Should the docs be updated to reflect this (i.e., it is intended), or
should I file a bug ticket?
Note, my settings contain:
USE_TZ = True
TIME_ZONE = 'UTC'
USE_L10N = True
The datetime in question was created via `timezone.now()`
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/django-developers?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
