Removed extra characters in docs header underlines.
This commit is contained in:
parent
7edeeb74fe
commit
a3af8c99d9
|
@ -11,7 +11,7 @@ Problems running ``django-admin``
|
|||
=================================
|
||||
|
||||
"command not found: `django-admin`"
|
||||
------------------------------------
|
||||
-----------------------------------
|
||||
|
||||
:doc:`django-admin </ref/django-admin>` should be on your system path if you
|
||||
installed Django via ``python setup.py``. If it's not on your path, you can
|
||||
|
|
|
@ -15,7 +15,7 @@ API reference
|
|||
=============
|
||||
|
||||
``CheckMessage``
|
||||
-----------------
|
||||
----------------
|
||||
|
||||
.. class:: CheckMessage(level, msg, hint=None, obj=None, id=None)
|
||||
|
||||
|
|
|
@ -53,7 +53,7 @@ would for any other project. We provide some tips for selected databases:
|
|||
* :doc:`install/spatialite`
|
||||
|
||||
Create a New Project
|
||||
------------------------
|
||||
--------------------
|
||||
|
||||
Use the standard ``django-admin`` script to create a project called
|
||||
``geodjango``:
|
||||
|
|
|
@ -425,7 +425,7 @@ rendering. For more details, see the :doc:`TemplateResponse documentation
|
|||
</ref/template-response>`.
|
||||
|
||||
Context variables
|
||||
------------------
|
||||
-----------------
|
||||
|
||||
When customizing the templates for the
|
||||
:func:`~django.contrib.sitemaps.views.index` and
|
||||
|
|
|
@ -604,7 +604,7 @@ specific to SQLite that you should be aware of.
|
|||
.. _sqlite-string-matching:
|
||||
|
||||
Substring matching and case sensitivity
|
||||
-----------------------------------------
|
||||
---------------------------------------
|
||||
|
||||
For all SQLite versions, there is some slightly counter-intuitive behavior when
|
||||
attempting to match some types of strings. These are triggered when using the
|
||||
|
|
|
@ -356,7 +356,7 @@ respect to the month.
|
|||
Like :attr:`~Field.unique_for_date` and :attr:`~Field.unique_for_month`.
|
||||
|
||||
``verbose_name``
|
||||
-------------------
|
||||
----------------
|
||||
|
||||
.. attribute:: Field.verbose_name
|
||||
|
||||
|
@ -365,7 +365,7 @@ will automatically create it using the field's attribute name, converting
|
|||
underscores to spaces. See :ref:`Verbose field names <verbose-field-names>`.
|
||||
|
||||
``validators``
|
||||
-------------------
|
||||
--------------
|
||||
|
||||
.. attribute:: Field.validators
|
||||
|
||||
|
@ -415,7 +415,7 @@ guaranteed to fit numbers from ``-9223372036854775808`` to
|
|||
:class:`~django.forms.TextInput`.
|
||||
|
||||
``BinaryField``
|
||||
-------------------
|
||||
---------------
|
||||
|
||||
.. class:: BinaryField(**options)
|
||||
|
||||
|
|
|
@ -28,7 +28,7 @@ options`_.
|
|||
Creates an index (B-Tree) in the database.
|
||||
|
||||
``fields``
|
||||
-----------
|
||||
----------
|
||||
|
||||
.. attribute:: Index.fields
|
||||
|
||||
|
|
|
@ -302,7 +302,7 @@ Django quotes column and table names behind the scenes.
|
|||
human_readable_permission_name)``.
|
||||
|
||||
``default_permissions``
|
||||
------------------------------
|
||||
-----------------------
|
||||
|
||||
.. attribute:: Options.default_permissions
|
||||
|
||||
|
|
|
@ -1488,7 +1488,7 @@ Monday and so on.
|
|||
.. setting:: FIXTURE_DIRS
|
||||
|
||||
``FIXTURE_DIRS``
|
||||
-----------------
|
||||
----------------
|
||||
|
||||
Default: ``[]`` (Empty list)
|
||||
|
||||
|
@ -1949,7 +1949,7 @@ See :tfilter:`allowed date format strings <date>`. See also
|
|||
.. setting:: NUMBER_GROUPING
|
||||
|
||||
``NUMBER_GROUPING``
|
||||
--------------------
|
||||
-------------------
|
||||
|
||||
Default: ``0``
|
||||
|
||||
|
|
|
@ -147,7 +147,7 @@ using one of these decorators::
|
|||
front_page = last_modified(latest_entry)(front_page)
|
||||
|
||||
Use ``condition`` when testing both conditions
|
||||
------------------------------------------------
|
||||
----------------------------------------------
|
||||
|
||||
It might look nicer to some people to try and chain the ``etag`` and
|
||||
``last_modified`` decorators if you want to test both preconditions. However,
|
||||
|
|
|
@ -1349,7 +1349,7 @@ Or use a common ancestor to hold the :class:`~django.db.models.AutoField`::
|
|||
pass
|
||||
|
||||
Field name "hiding" is not permitted
|
||||
-------------------------------------
|
||||
------------------------------------
|
||||
|
||||
In normal Python class inheritance, it is permissible for a child class to
|
||||
override any attribute from the parent class. In Django, this isn't usually
|
||||
|
|
|
@ -549,7 +549,7 @@ solution is to use ``db_manager()``, like this::
|
|||
``db_manager()`` returns a copy of the manager bound to the database you specify.
|
||||
|
||||
Using ``get_queryset()`` with multiple databases
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If you're overriding ``get_queryset()`` on your manager, be sure to
|
||||
either call the method on the parent (using ``super()``) or do the
|
||||
|
|
|
@ -1638,7 +1638,7 @@ That's it. Your translations are ready for use.
|
|||
files by default then you will need to reconfigure it.
|
||||
|
||||
Troubleshooting: ``gettext()`` incorrectly detects ``python-format`` in strings with percent signs
|
||||
---------------------------------------------------------------------------------------------------
|
||||
--------------------------------------------------------------------------------------------------
|
||||
|
||||
In some cases, such as strings with a percent sign followed by a space and a
|
||||
:ref:`string conversion type <old-string-formatting>` (e.g.
|
||||
|
|
Loading…
Reference in New Issue