#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):
It didn't give a clue because I didn't know that there are two different
TIME_ZONE settings, so that sentence was meaningless to me; the phrase
"the general TIME_ZONE setting" tells you nothing if you don't know that
what you're looking for ''is'' the "general TIME_ZONE setting" and not
whatever unexplained thing this is that you're looking at.
The CACHES.BACKEND and TEMPLATES.BACKEND settings don't have the same
confusion as neither of them is a "general" setting and each of them
starts with the words "The cache backend to use" or "The template backend
to use" so there's no way you could be looking at one thinking it's the
other.
--
Ticket URL: <https://code.djangoproject.com/ticket/28625#comment:7>
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.0bd7e1ec80596f3c5e81ea7b1ce629fe%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
