[Django] #28829: Timezone is recognized only when provided in CamelCase
Django
------------------------------------------------+------------------------
Reporter: shanushaan | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (System checks) | Version: 1.11
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
------------------------------------------------+------------------------
Initially the settings.py had the
time_zone = "ASIA/KOLKATA"
which was not recognized by django and gave the exception
pytz.exceptions.UnknownTimeZoneError: 'asia/kolkata'
when changed the code to
time_zone = "Asia/Kolkata"
it started the server fine.
--
Ticket URL: <https://code.djangoproject.com/ticket/28829>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
Django
Reporter: shanushaan | Owner: nobody
Type: Uncategorized | Status: new
checks) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Tim Graham):
What change are you proposing? The casing in the
[https://en.wikipedia.org/wiki/List_of_tz_database_time_zones list of
accepted timezones] that the documentation points to looks correct.
--
Ticket URL: <https://code.djangoproject.com/ticket/28829#comment:1>
Django
Reporter: shanushaan | Owner: nobody
Type: Uncategorized | Status: new
checks) |
Severity: Normal | Resolution:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Comment (by Piotr Domański):
Firstly it is not because of CamelCase but because of matching value of
this setting to file in /usr/share/zoneinfo.
If this file does not exist than exception is raised.
Secondly i am not sure should this ticket be fixed.
If there are two different timezones which are equal when we ignore cases,
than it is ambigous, which timezone should be chosen.
Of course it is possible to match this file without taking care of case
sensivity, but to submit PR i need decision what to.
--
Ticket URL: <https://code.djangoproject.com/ticket/28829#comment:2>
Django
Reporter: shanushaan | Owner: nobody
Type: Uncategorized | Status: closed
Component: Core (Other) | Version: 1.11
Severity: Normal | Resolution: needsinfo
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
Changes (by Tim Graham):
* status: new => closed
* resolution: => needsinfo
* component: Core (System checks) => Core (Other)
Comment:
Absent some clarification of what this ticket is suggesting, the current
behavior seems fine to me.
--
Ticket URL: <https://code.djangoproject.com/ticket/28829#comment:3>