#32873 closed Cleanup/optimization (fixed)
Deprecate USE_L10N setting.
| Reported by: | Carlton Gibson | Owned by: | Claude Paroz |
|---|---|---|---|
| Component: | Internationalization | Version: | dev |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Ready for checkin | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
There's a proposal from Claude to remove the USE_L10N setting.
My motivations are:
- one less setting
- simplication of the code and logic regarding USE_18N/USE_L10N/USE_TZ
settings
- a user-friendly default behavior
Accepting on the basis of the discussion there.
Change History (12)
comment:1 by , 3 years ago
| Patch needs improvement: | unset |
|---|
comment:3 by , 3 years ago
| Summary: | Remove USE_L10N setting → Deprecate USE_L10N setting. |
|---|
Claude's PR should be used when USE_L10N will be removed in Django 5.0.
comment:5 by , 3 years ago
| Triage Stage: | Accepted → Ready for checkin |
|---|
follow-up: 8 comment:7 by , 3 years ago
Mariusz, I still rebased my original patch, as it may be of some help at the time of the deprecation removal. I know code might move a lot until then, but still in the case it might be useful, I'm keeping that branch on my fork: https://github.com/claudep/django/tree/remove_use_l10n
comment:8 by , 3 years ago
Replying to Claude Paroz:
Mariusz, I still rebased my original patch, as it may be of some help at the time of the deprecation removal. I know code might move a lot until then, but still in the case it might be useful, I'm keeping that branch on my fork: https://github.com/claudep/django/tree/remove_use_l10n
Many thanks!
Should be ready for review.