Opened 13 years ago
Closed 13 years ago
#17274 closed Bug (fixed)
Regression: "TIME_ZONE = None" fails if "USE_TZ = True"
Reported by: | Daniel Swarbrick | Owned by: | nobody |
---|---|---|---|
Component: | Internationalization | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
Until the recent addition of TZ-aware dates, setting "TIME_ZONE = None" in settings.py has worked fine, as stated in the comments:
# On Unix systems, a value of None will cause Django to use the same
# timezone as the operating system.
However, if "USE_TZ = True", any output of datetime objects in a template results in:
AttributeError: 'NoneType' object has no attribute 'upper'
Apparently the TZ is not being determined prior the TZ-conversion code.
Tested with svn trunk r17133.
Note:
See TracTickets
for help on using tickets.
In [17134]: