#19480: Allow suport for custom i18n backends in Django
-------------------------------------+-------------------------------------
Reporter: rtnpro@… | Owner: nobody
Type: New feature | Status: closed
Component: | Version: master
Internationalization | Resolution: duplicate
Severity: Normal | Triage Stage:
Keywords: i18n, backend | Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by jezdez):
I'm not a fan of that implementation as it makes a private API (real/null)
public. Instead there should simply be a `I18N_BACKEND` setting that if
set would enable the system and if left unset disable it. The `USE_I18N`
setting would be deprecated in that case. The scope of this ticket is also
too limited compared to #14974, so closing it as duplicate is correct,
while it's also not a complete fix for #14974.
--
Ticket URL: <https://code.djangoproject.com/ticket/19480#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
