Capitalized "Python" in docs.
This commit is contained in:
parent
5c35b4a8c9
commit
2fbea621e6
|
@ -260,7 +260,7 @@ Compressing JavaScript
|
|||
~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
To simplify the process of providing optimized JavaScript code, Django
|
||||
includes a handy python script which should be used to create a "minified"
|
||||
includes a handy Python script which should be used to create a "minified"
|
||||
version. To run it::
|
||||
|
||||
python django/contrib/admin/bin/compress.py
|
||||
|
|
|
@ -305,7 +305,7 @@ model::
|
|||
This is generally the operation you would use to create
|
||||
:ref:`data migrations <data-migrations>`, run
|
||||
custom data updates and alterations, and anything else you need access to an
|
||||
ORM and/or python code for.
|
||||
ORM and/or Python code for.
|
||||
|
||||
If you're upgrading from South, this is basically the South pattern as an
|
||||
operation - one or two methods for forwards and backwards, with an ORM and
|
||||
|
|
|
@ -57,7 +57,7 @@ Usage examples::
|
|||
|
||||
.. warning::
|
||||
|
||||
A python value passed to ``Coalesce`` on MySQL may be converted to an
|
||||
A Python value passed to ``Coalesce`` on MySQL may be converted to an
|
||||
incorrect type unless explicitly cast to the correct database type:
|
||||
|
||||
>>> from django.db.models.expressions import RawSQL
|
||||
|
@ -121,7 +121,7 @@ Usage example::
|
|||
>>> comments = Comment.objects.annotate(last_updated=Greatest('modified', 'blog__modified'))
|
||||
>>> annotated_comment = comments.get()
|
||||
|
||||
``annotated_comment.last_updated`` will be the most recent of
|
||||
``annotated_comment.last_updated`` will be the most recent of
|
||||
``blog.modified`` and ``comment.modified``.
|
||||
|
||||
.. warning::
|
||||
|
|
|
@ -735,7 +735,7 @@ will be handed over to interested members of the community.
|
|||
~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
The markup contrib module has been deprecated and will follow an accelerated
|
||||
deprecation schedule. Direct use of python markup libraries or 3rd party tag
|
||||
deprecation schedule. Direct use of Python markup libraries or 3rd party tag
|
||||
libraries is preferred to Django maintaining this functionality in the
|
||||
framework.
|
||||
|
||||
|
|
|
@ -359,7 +359,7 @@ from::
|
|||
return True
|
||||
|
||||
Finally, in the settings file, we add the following (substituting
|
||||
``path.to.`` with the actual python path to the module(s) where the
|
||||
``path.to.`` with the actual Python path to the module(s) where the
|
||||
routers are defined)::
|
||||
|
||||
DATABASE_ROUTERS = ['path.to.AuthRouter', 'path.to.PrimaryReplicaRouter']
|
||||
|
|
|
@ -1858,7 +1858,7 @@ way Django does translation:
|
|||
* The string domain is ``django`` or ``djangojs``. This string domain is
|
||||
used to differentiate between different programs that store their data
|
||||
in a common message-file library (usually ``/usr/share/locale/``). The
|
||||
``django`` domain is used for python and template translation strings
|
||||
``django`` domain is used for Python and template translation strings
|
||||
and is loaded into the global translation catalogs. The ``djangojs``
|
||||
domain is only used for JavaScript translation catalogs to make sure
|
||||
that those are as small as possible.
|
||||
|
|
Loading…
Reference in New Issue