#13702 closed (fixed)
DATE_FORMAT et al not used when USE_L10N is False
Reported by: | Karen Tracey | Owned by: | Jannis Leidel |
---|---|---|---|
Component: | Internationalization | Version: | 1.2 |
Severity: | Keywords: | ||
Cc: | Marti Raudsepp | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
If I set USE_L10N to False in settings.py, dates in the admin changelist (at least) do not fall back from using the locale DATE_FORMAT to the settings DATE_FORMAT as is implied by the doc. Rather the no-frills date str/unicode formatting is used. Problem may be that the localize function in utils (http://code.djangoproject.com/browser/django/tags/releases/1.2.1/django/utils/formats.py#L77) does not do anything if USE_L10N is False, or perhaps the caller is supposed to do something else if USE_L10N if False...but the admin, at least, does not: http://code.djangoproject.com/browser/django/tags/releases/1.2.1/django/contrib/admin/util.py#L316. Some code somewhere ought to be falling back to the old settings values, but as far as I can see none is.
Change History (5)
comment:1 by , 14 years ago
comment:2 by , 14 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Triage Stage: | Unreviewed → Accepted |
comment:3 by , 14 years ago
Cc: | added |
---|
comment:4 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
There is another ticket realted DATE_FORMAT and USE_L10N http://code.djangoproject.com/ticket/13621. In the list Malcom has explained that they made some changes on 1.2.1 to avoid some threading issues with Python date conversion functions,but it seems the chage has other side effects.