#20477 closed New feature (fixed)
Allow list of modules for FORMAT_MODULE_PATH
Reported by: | mbrochh | Owned by: | mbrochh |
---|---|---|---|
Component: | Internationalization | Version: | dev |
Severity: | Normal | Keywords: | localization, format files |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | yes |
Easy pickings: | no | UI/UX: | no |
Description
Currently the FORMAT_MODULE_PATH setting (see https://docs.djangoproject.com/en/dev/topics/i18n/formatting/#creating-custom-format-files) only allows a string as a value. This is not optimal because it prevents us from shipping custom format strings with reusable apps.
Imagine the following situation:
- You have created a reusable app that provides a new custom format string for displaying person names
- You have created a reusable app that heavily relies on the format string for SHORT_DATE to be in a specific format and thus provides a formats folder
- In your django project you would like to override some of the other standard format strings
So in this situation you would have one project and two apps each having a formats folder. But we can only set FORMAT_MODULE_PATH to one path.
The code that currently loads those format strings is actually able to deal with a list (see https://github.com/django/django/blob/master/django/utils/formats.py#L67), because first it loads Django's standard formats (see https://github.com/django/django/blob/master/django/utils/formats.py#L46) and then it loads the module defined in FORMAT_MODULE_PATH. It then reverses the list, so that our setting overrides the values of Django's default.
In order to solve this problem, we have copied all this format string loading code and basically just changed line 47, turning the if-clause into a for loop (see https://github.com/bitmazk/django-libs/blob/master/django_libs/format_utils.py#L51).
Now we can set the setting like so:
CUSTOM_FORMAT_MODULE_PATH = [
'my_django_project.formats',
'my_person_name_app.formats',
'my_short_date_app.formats',
]
After working with Django professionally since more than 2 years, I would love to make this my first contribution. If I provided a patch (with tests and documentation), would there be any chance that it will be merged?
Change History (11)
comment:1 by , 12 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 12 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
comment:3 by , 12 years ago
Created pull request: https://github.com/django/django/pull/1236
I actually only replaced one line of Django code with a few more lines. The change is quite trivial.
The original code was not yet covered by the test suite, so I added new tests and increased the test coverage for utils/formats.py
.
I also updated to docs.
Hope this is all good :)
comment:4 by , 12 years ago
Has patch: | set |
---|
comment:5 by , 12 years ago
Update: I added some comments to the pull request to make codereview easier.
comment:6 by , 11 years ago
Patch needs improvement: | set |
---|
There are comments on the pull request indicating it needs improvement.
comment:7 by , 11 years ago
Easy pickings: | unset |
---|
comment:8 by , 11 years ago
@timo I have done the requested improvement: https://github.com/django/django/pull/1236
comment:9 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Yes, it makes sense for me.