#17379: Don't force output of the 'shell' management command to en-us
-------------------------------------+-------------------------------------
Reporter: chrischambers | Owner: ramiro
Type: Bug | Status: assigned
Component: | Version: master
Internationalization | Resolution:
Severity: Normal | Triage Stage: Accepted
Keywords: management, shell, | Needs documentation: 1
i18n, l10n, en-us, translation, | Patch needs improvement: 1
documentation | UI/UX: 0
Has patch: 1 |
Needs tests: 0 |
Easy pickings: 1 |
-------------------------------------+-------------------------------------
Comment (by ramiro):
I've opened #19730 to track the unfolding of the meaning of the
`can_import_settings` option.
I'm also changing the title of this one from "Silent translation of all
./manage.py commands to en-us unexpected/undocumented" "Don't force output
of the 'shell' management command to en-us" because the fact that by
default commands use the en_US locale isn't undocumented (see "Management
commands and locales" note in https://docs.djangoproject.com/en/1.4/howto
/custom-management-commands/) and hence it shouldn't be unexpected.
Let's discuss in this ticket if it's possible to the 'shell' command to
use the locale configured by the developer for the project if USE_I18N is
active.
--
Ticket URL: <https://code.djangoproject.com/ticket/17379#comment:14>
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 django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
