mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 10:59:45 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4

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

Browse source 
Sphinx generates left single quotes for apostrophes after
code markup, when right single quotes are required. The
easiest way to fix this is just by inserting the unicode
character for a right single quote.

Instances of the problem were found by looking for
">‘" in the generated HTML.
This commit is contained in:
Dominic Rodger 2013-08-05 17:23:26 +01:00 • committed by Tim Graham
parent 0b771fcf29
commit c33d1ca1d9
20 changed files with 30 additions and 30 deletions
Download patch file Download diff file Expand all files Collapse all files

8
docs/howto/error-reporting.txt
View file

@ -120,8 +120,8 @@ Filtering sensitive information
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
@ -164,7 +164,7 @@ production environment (that is, where :setting:`DEBUG` is set to ``False``):
.. 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::
@ -232,7 +232,7 @@ own filter class and tell Django to use it via the
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):