#28625: DATABASES TIME_ZONE setting may be confused with TIME_ZONE
-------------------------------------+-------------------------------------
Reporter: Jon Ribbens | Owner: Jon
Type: | Ribbens
Cleanup/optimization | Status: assigned
Component: Documentation | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jon Ribbens):
There's a general principle of course that if you are an expert in
something it can be very hard to know what will and will not be obvious to
non-experts. I couldn't comment on the probability of confusion in
general, all I can offer is the sure and certain fact that I was indeed
confused and it caused me a noticeable amount of wasted time trying to
work out how I was supposed to get times to be displayed in my chosen time
zone and investigating what I was supposed to do about TIME_ZONE having
been set by `django-admin startproject` in apparent contradiction to the
documentation which seemed to say that it must not be set if USE_TZ is set
(since I'm using PostgreSQL).
--
Ticket URL: <https://code.djangoproject.com/ticket/28625#comment:5>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" 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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.4d8168863ff288fa691e8c9728360188%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
