    you counted on English translations to be activated in management commands,
    this will not happen any longer. It might be that new database migrations are
    generated (once) after migrating to 1.8.
  
  .. _deprecated-features-1.8:
  
  Features deprecated in 1.8
  ==========================
  
 
</s> remove from django.conf import settings
 </s> add  </s> remove             # get_language returns settings.LANGUAGE_CODE for NullTranslations instances
            self.assertEqual(out.getvalue(), "%s\n" % settings.LANGUAGE_CODE)
 </s> add             self.assertEqual(out.getvalue(), "") </s> remove     def test_default_en_us_locale_set(self):
        # Forces en_us when set to true
 </s> add     def test_deactivate_locale_set(self):
        # Deactivate translation when set to true </s> remove             self.assertEqual(get_language(), settings.LANGUAGE_CODE)
 </s> add             self.assertEqual(get_language(), None) </s> remove                 self.assertEqual(get_language(), settings.LANGUAGE_CODE)
 </s> add                 self.assertEqual(get_language(), None)
* :func:`django.utils.translation.get_language()` now returns ``None`` instead
  of :setting:`LANGUAGE_CODE` when translations are temporarily deactivated.

    you counted on English translations to be activated in management commands,
    this will not happen any longer. It might be that new database migrations are
    generated (once) after migrating to 1.8.
  
* :func:`django.utils.translation.get_language()` now returns ``None`` instead
  of :setting:`LANGUAGE_CODE` when translations are temporarily deactivated.

  .. _deprecated-features-1.8:
  
  Features deprecated in 1.8
  ==========================
  
keep keep keep add keep keep keep keep keep
 Fixed #24073 -- Returned None for get_language when translations are deactivated

This fixes a regression caused by f7c287fca9. Thanks Markus Holtermann
for identifying the regression. 
docs/releases/1.8.txt