#28829: Timezone is recognized only when provided in CamelCase
-------------------------------------+-------------------------------------
Reporter: shanushaan | Owner: nobody
Type: Uncategorized | Status: new
Component: Core (System | Version: 1.11
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 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 <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/068.aa8e1184e87af0236e966390806623a5%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
