  :func:`~django.contrib.auth.decorators.login_required` decorator.
  
  .. versionchanged:: 1.5
  
  This setting now also accepts view function names and
  :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
  configuration duplication since you no longer have to define the URL in two
  places (``settings`` and URLconf).
  For backward compatibility reasons the default remains unchanged.
  
  .. setting:: LOGOUT_URL
  
  LOGOUT_URL
  ----------
 
</s> remove This setting now also accepts view function names and
:ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
configuration duplication since you no longer have to define the URL in two
places (``settings`` and URLconf).
For backward compatibility reasons the default remains unchanged.
 </s> add     This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged. </s> remove     The :setting:`settings.LOGIN_URL <LOGIN_URL>` also accepts
    view function names and :ref:`named URL patterns <naming-url-patterns>`.
    This allows you to freely remap your login view within your URLconf
    without having to update the setting.
 </s> add         The :setting:`settings.LOGIN_URL <LOGIN_URL>` also accepts
        view function names and :ref:`named URL patterns <naming-url-patterns>`.
        This allows you to freely remap your login view within your URLconf
        without having to update the setting. </s> remove         ``success_url`` may contain dictionary string formatting, which
        will be interpolated against the object's field attributes. For
        example, you could use ``success_url="/parent/%(parent_id)s/"`` to
        redirect to a URL composed out of the ``parent_id`` field on a model.
 </s> add             ``success_url`` may contain dictionary string formatting, which
            will be interpolated against the object's field attributes. For
            example, you could use ``success_url="/parent/%(parent_id)s/"`` to
            redirect to a URL composed out of the ``parent_id`` field on a model. </s> remove See also :doc:`Python 3 compatibility </topics/python3>`.
 </s> add     See also :doc:`Python 3 compatibility </topics/python3>`. </s> remove When the :func:`atomic` decorator is nested, it creates a savepoint to allow
partial commit or rollback. You're strongly encouraged to use :func:`atomic`
rather than the functions described below, but they're still part of the
public API, and there's no plan to deprecate them.
 </s> add     When the :func:`atomic` decorator is nested, it creates a savepoint to allow
    partial commit or rollback. You're strongly encouraged to use :func:`atomic`
    rather than the functions described below, but they're still part of the
    public API, and there's no plan to deprecate them.
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
  :func:`~django.contrib.auth.decorators.login_required` decorator.
  
  .. versionchanged:: 1.5
  
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
    This setting now also accepts view function names and
    :ref:`named URL patterns <naming-url-patterns>` which can be used to reduce
    configuration duplication since you no longer have to define the URL in two
    places (``settings`` and URLconf).
    For backward compatibility reasons the default remains unchanged.
  
  .. setting:: LOGOUT_URL
  
  LOGOUT_URL
  ----------
keep keep keep keep replace replace replace replace replace keep keep keep keep keep
 Adapted uses of versionchanged/versionadded to the new form.

Refs #20104. 
docs/ref/settings.txt