Loading docs/conf.py +1 −0 Original line number Diff line number Diff line Loading @@ -110,6 +110,7 @@ intersphinx_mapping = { 'python': ('http://docs.python.org/2.7', None), 'sphinx': ('http://sphinx.pocoo.org/', None), 'six': ('http://packages.python.org/six/', None), 'simplejson': ('http://simplejson.readthedocs.org/en/latest/', None), } # Python's docs don't change every week. Loading docs/howto/error-reporting.txt +10 −10 Original line number Diff line number Diff line Loading @@ -123,7 +123,7 @@ 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:`HttpRequest`'s :ref:`attributes<httprequest-attributes>`. :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 Loading Loading @@ -165,11 +165,11 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. function:: sensitive_post_parameters(*parameters) If one of your views receives an :class:`HttpRequest` object with :attr:`POST parameters<HttpRequest.POST>` susceptible to contain sensitive information, you may prevent the values of those parameters from being included in the error reports using the ``sensitive_post_parameters`` decorator:: If one of your views receives an :class:`~django.http.HttpRequest` object with :attr:`POST parameters<django.http.HttpRequest.POST>` susceptible to contain sensitive information, you may prevent the values of those parameters from being included in the error reports using the ``sensitive_post_parameters`` decorator:: from django.views.decorators.debug import sensitive_post_parameters Loading Loading @@ -198,10 +198,10 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. versionchanged:: 1.4 Since version 1.4, all POST parameters are systematically filtered out of error reports for certain :mod:`contrib.views.auth` views (``login``, ``password_reset_confirm``, ``password_change``, and ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent the leaking of sensitive information such as user passwords. error reports for certain :mod:`django.contrib.auth.views` views ( ``login``, ``password_reset_confirm``, ``password_change``, and ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent the leaking of sensitive information such as user passwords. .. _custom-error-reports: Loading docs/intro/tutorial02.txt +3 −3 Original line number Diff line number Diff line Loading @@ -398,9 +398,9 @@ That adds a "Filter" sidebar that lets people filter the change list by the :alt: Polls change list page, updated The type of filter displayed depends on the type of field you're filtering on. Because ``pub_date`` is a :class:`~django.db.models.fields.DateTimeField`, Django knows to give appropriate filter options: "Any date," "Today," "Past 7 days," "This month," "This year." Because ``pub_date`` is a :class:`~django.db.models.DateTimeField`, Django knows to give appropriate filter options: "Any date," "Today," "Past 7 days," "This month," "This year." This is shaping up well. Let's add some search capability:: Loading docs/intro/tutorial04.txt +4 −3 Original line number Diff line number Diff line Loading @@ -98,9 +98,10 @@ This code includes a few things we haven't covered yet in this tutorial: <django.http.HttpRequest.POST>` in our code, to ensure that data is only altered via a POST call. * ``request.POST['choice']`` will raise :exc:`KeyError` if ``choice`` wasn't provided in POST data. The above code checks for :exc:`KeyError` and redisplays the poll form with an error message if ``choice`` isn't given. * ``request.POST['choice']`` will raise :exc:`~exceptions.KeyError` if ``choice`` wasn't provided in POST data. The above code checks for :exc:`~exceptions.KeyError` and redisplays the poll form with an error message if ``choice`` isn't given. * After incrementing the choice count, the code returns an :class:`~django.http.HttpResponseRedirect` rather than a normal Loading docs/ref/contrib/comments/models.txt +2 −3 Original line number Diff line number Diff line Loading @@ -11,12 +11,12 @@ The built-in comment models .. attribute:: content_object A :class:`~django.contrib.contettypes.generic.GenericForeignKey` A :class:`~django.contrib.contenttypes.generic.GenericForeignKey` attribute pointing to the object the comment is attached to. You can use this to get at the related object (i.e. ``my_comment.content_object``). Since this field is a :class:`~django.contrib.contettypes.generic.GenericForeignKey`, it's :class:`~django.contrib.contenttypes.generic.GenericForeignKey`, it's actually syntactic sugar on top of two underlying attributes, described below. Loading Loading @@ -77,4 +77,3 @@ The built-in comment models ``True`` if the comment was removed. Used to keep track of removed comments instead of just deleting them. Loading
docs/conf.py +1 −0 Original line number Diff line number Diff line Loading @@ -110,6 +110,7 @@ intersphinx_mapping = { 'python': ('http://docs.python.org/2.7', None), 'sphinx': ('http://sphinx.pocoo.org/', None), 'six': ('http://packages.python.org/six/', None), 'simplejson': ('http://simplejson.readthedocs.org/en/latest/', None), } # Python's docs don't change every week. Loading
docs/howto/error-reporting.txt +10 −10 Original line number Diff line number Diff line Loading @@ -123,7 +123,7 @@ 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:`HttpRequest`'s :ref:`attributes<httprequest-attributes>`. :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 Loading Loading @@ -165,11 +165,11 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. function:: sensitive_post_parameters(*parameters) If one of your views receives an :class:`HttpRequest` object with :attr:`POST parameters<HttpRequest.POST>` susceptible to contain sensitive information, you may prevent the values of those parameters from being included in the error reports using the ``sensitive_post_parameters`` decorator:: If one of your views receives an :class:`~django.http.HttpRequest` object with :attr:`POST parameters<django.http.HttpRequest.POST>` susceptible to contain sensitive information, you may prevent the values of those parameters from being included in the error reports using the ``sensitive_post_parameters`` decorator:: from django.views.decorators.debug import sensitive_post_parameters Loading Loading @@ -198,10 +198,10 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``): .. versionchanged:: 1.4 Since version 1.4, all POST parameters are systematically filtered out of error reports for certain :mod:`contrib.views.auth` views (``login``, ``password_reset_confirm``, ``password_change``, and ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent the leaking of sensitive information such as user passwords. error reports for certain :mod:`django.contrib.auth.views` views ( ``login``, ``password_reset_confirm``, ``password_change``, and ``add_view`` and ``user_change_password`` in the ``auth`` admin) to prevent the leaking of sensitive information such as user passwords. .. _custom-error-reports: Loading
docs/intro/tutorial02.txt +3 −3 Original line number Diff line number Diff line Loading @@ -398,9 +398,9 @@ That adds a "Filter" sidebar that lets people filter the change list by the :alt: Polls change list page, updated The type of filter displayed depends on the type of field you're filtering on. Because ``pub_date`` is a :class:`~django.db.models.fields.DateTimeField`, Django knows to give appropriate filter options: "Any date," "Today," "Past 7 days," "This month," "This year." Because ``pub_date`` is a :class:`~django.db.models.DateTimeField`, Django knows to give appropriate filter options: "Any date," "Today," "Past 7 days," "This month," "This year." This is shaping up well. Let's add some search capability:: Loading
docs/intro/tutorial04.txt +4 −3 Original line number Diff line number Diff line Loading @@ -98,9 +98,10 @@ This code includes a few things we haven't covered yet in this tutorial: <django.http.HttpRequest.POST>` in our code, to ensure that data is only altered via a POST call. * ``request.POST['choice']`` will raise :exc:`KeyError` if ``choice`` wasn't provided in POST data. The above code checks for :exc:`KeyError` and redisplays the poll form with an error message if ``choice`` isn't given. * ``request.POST['choice']`` will raise :exc:`~exceptions.KeyError` if ``choice`` wasn't provided in POST data. The above code checks for :exc:`~exceptions.KeyError` and redisplays the poll form with an error message if ``choice`` isn't given. * After incrementing the choice count, the code returns an :class:`~django.http.HttpResponseRedirect` rather than a normal Loading
docs/ref/contrib/comments/models.txt +2 −3 Original line number Diff line number Diff line Loading @@ -11,12 +11,12 @@ The built-in comment models .. attribute:: content_object A :class:`~django.contrib.contettypes.generic.GenericForeignKey` A :class:`~django.contrib.contenttypes.generic.GenericForeignKey` attribute pointing to the object the comment is attached to. You can use this to get at the related object (i.e. ``my_comment.content_object``). Since this field is a :class:`~django.contrib.contettypes.generic.GenericForeignKey`, it's :class:`~django.contrib.contenttypes.generic.GenericForeignKey`, it's actually syntactic sugar on top of two underlying attributes, described below. Loading Loading @@ -77,4 +77,3 @@ The built-in comment models ``True`` if the comment was removed. Used to keep track of removed comments instead of just deleting them.