Fixed #20852 - Fixed incorrectly generated left quotes in docs.

----------

All attributes can be set in your derived class and can be used in

:class:`BaseCommand`'s :ref:`subclasses<ref-basecommand-subclasses>`.

:class:`BaseCommand`’s :ref:`subclasses<ref-basecommand-subclasses>`.

.. attribute:: BaseCommand.args

.. admonition:: Implementing a constructor in a subclass

  If you implement ``__init__`` in your subclass of :class:`BaseCommand`,

  you must call :class:`BaseCommand`'s ``__init__``.

  you must call :class:`BaseCommand`’s ``__init__``.

  .. code-block:: python

Error reports are really helpful for debugging errors, so it is generally

useful to record as much relevant information about those errors as possible.

For example, by default Django records the `full traceback`_ for the

exception raised, each `traceback frame`_'s local variables, and the

:class:`~django.http.HttpRequest`'s :ref:`attributes<httprequest-attributes>`.

exception raised, each `traceback frame`_’s local variables, and the

:class:`~django.http.HttpRequest`’s :ref:`attributes<httprequest-attributes>`.

However, sometimes certain types of information may be too sensitive and thus

may not be appropriate to be kept track of, for example a user's password or

    .. admonition:: When using mutiple decorators

        If the variable you want to hide is also a function argument (e.g.

        '``user``' in the following example), and if the decorated function has

        '``user``’ in the following example), and if the decorated function has

        mutiple decorators, then make sure to place ``@sensitive_variables`` at

        the top of the decorator chain. This way it will also hide the function

        argument as it gets passed through the other decorators::

    DEFAULT_EXCEPTION_REPORTER_FILTER = 'path.to.your.CustomExceptionReporterFilter'

You may also control in a more granular way which filter to use within any

given view by setting the ``HttpRequest``'s ``exception_reporter_filter``

given view by setting the ``HttpRequest``’s ``exception_reporter_filter``

attribute::

    def my_view(request):

Fortunately, there's a little bug in the ``polls`` application for us to fix

right away: the ``Poll.was_published_recently()`` method returns ``True`` if

the ``Poll`` was published within the last day (which is correct) but also if

the ``Poll``'s ``pub_date`` field is in the future (which certainly isn't).

the ``Poll``’s ``pub_date`` field is in the future (which certainly isn't).

You can see this in the Admin; create a poll whose date lies in the future;

you'll see that the ``Poll`` change list claims it was published recently.

    .. attribute:: date_field

        The name of the ``DateField`` or ``DateTimeField`` in the

        ``QuerySet``'s model that the date-based archive should use to

        ``QuerySet``’s model that the date-based archive should use to

        determine the list of objects to display on the page.

        When :doc:`time zone support </topics/i18n/timezones>` is enabled and

    The embedded jQuery has been upgraded from 1.4.2 to 1.9.1.

The :class:`ModelAdmin` class requires jQuery by default, so there is no need

to add jQuery to your ``ModelAdmin``'s list of media resources unless you have

to add jQuery to your ``ModelAdmin``’s list of media resources unless you have

a specifc need. For example, if you require the jQuery library to be in the

global namespace (for example when using third-party jQuery plugins) or if you

need a newer version of jQuery, you will have to include your own copy.