  This signal is sent when the value of a setting is changed through the
  :meth:`django.test.TestCase.setting` context manager or the
  :func:`django.test.utils.override_settings` decorator/context manager.
  
  Arguments sent with this signal:
  
  ``sender``
      The settings handler.
  
  ``setting``
 
</s> remove Sent when some :ref:`settings are overridden <overriding-settings>` with the
 </s> add This signal is sent when the value of a setting is changed through the </s> remove     Same as sender
 </s> add     The name of the setting. </s> remove     The new setting value.
 </s> add     The value of the setting after the change. For settings that initially
    don't exist, in the "teardown" phase, ``value`` is ``None``. </s> remove class OverrideSettingsHolder(UserSettingsHolder):
    """
    A custom setting holder that sends a signal upon change.
    """
    def __setattr__(self, name, value):
        UserSettingsHolder.__setattr__(self, name, value)
        setting_changed.send(sender=self.__class__, setting=name, value=value)


 </s> add 
It's actually sent twice: when the new value is applied ("setup") and when the
original value is restored ("teardown").

  This signal is sent when the value of a setting is changed through the
  :meth:`django.test.TestCase.setting` context manager or the
  :func:`django.test.utils.override_settings` decorator/context manager.
  
It's actually sent twice: when the new value is applied ("setup") and when the
original value is restored ("teardown").

  Arguments sent with this signal:
  
  ``sender``
      The settings handler.
  
  ``setting``
keep keep keep add keep keep keep keep keep keep
 Fixed #17895 -- Made override_settings send the setting_changed signal both when a setting is overridden and when it's restored.


git-svn-id: http://code.djangoproject.com/svn/django/trunk@17708 bcc190cf-cafb-0310-a4f2-bffc1f526a37 
docs/ref/signals.txt