#27981: date/time filter docs inaccurate about how localization works
--------------------------------------+------------------------------------
Reporter: Erdem Yılmaz | Owner: nobody
Type: Bug | Status: new
Component: Documentation | Version: 1.10
Severity: Normal | Resolution:
Keywords: template date filter | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Comment (by Claude Paroz):
> I just curious about why when USE_L10N is True, all dates and numbers
are now consistently localized by default even if some format setting
(DATE_FORMAT, TIME_FORMAT etc.) is present. In my opininon setting
something explicitly in the settings.py should have higher precedence than
a locale format
`DATE_FORMAT` and `TIME_FORMAT` always have a value from the global
settings (for the case where `USE_L10N` is False). So Django cannot know
if the settings are redefined at project level.
--
Ticket URL: <https://code.djangoproject.com/ticket/27981#comment:6>
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.8447549ca722c15cd7207e0d165e06cc%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
