From 3f951b1f94e50115824af404710a4b7c177cb03e Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Fri, 12 Jan 2018 14:17:53 -0500 Subject: [PATCH] [2.0.x] Fixed #29017 -- Updated BaseCommand.leave_locale_alone doc per refs #24073. Backport of b9cec9fa1fc50207ab68a59853c851a945c5db5e from master --- docs/howto/custom-management-commands.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/howto/custom-management-commands.txt b/docs/howto/custom-management-commands.txt index 77405a1622..e01a4138bc 100644 --- a/docs/howto/custom-management-commands.txt +++ b/docs/howto/custom-management-commands.txt @@ -252,7 +252,8 @@ All attributes can be set in your derived class and can be used in .. attribute:: BaseCommand.leave_locale_alone A boolean indicating whether the locale set in settings should be preserved - during the execution of the command instead of being forcibly set to 'en-us'. + during the execution of the command instead of translations being + deactivated. Default value is ``False``. @@ -260,9 +261,8 @@ All attributes can be set in your derived class and can be used in this option in your custom command if it creates database content that is locale-sensitive and such content shouldn't contain any translations (like it happens e.g. with :mod:`django.contrib.auth` permissions) as - making the locale differ from the de facto default 'en-us' might cause - unintended effects. See the `Management commands and locales`_ section - above for further details. + activating any locale might cause unintended effects. See the `Management + commands and locales`_ section above for further details. .. attribute:: BaseCommand.style