mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-26 03:39:11 +00:00
Code Issues 32 Releases Wiki Activity

Refs #36485 -- Removed double spaces after periods in sentences.

Browse Source
This commit is contained in:
Natalia 2025-08-22 12:36:48 -03:00 committed by nessita
parent 01a460f23e
commit 4286a23df6
80 changed files with 310 additions and 306 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/ref/contrib/admin/index.txt
View File

@ -1355,9 +1355,9 @@ subclass::
Custom template options
~~~~~~~~~~~~~~~~~~~~~~~
The :ref:`admin-overriding-templates` section describes how to override or extend
the default admin templates. Use the following options to override the default
templates used by the :class:`ModelAdmin` views:
The :ref:`admin-overriding-templates` section describes how to override or
extend the default admin templates. Use the following options to override the
default templates used by the :class:`ModelAdmin` views:
.. attribute:: ModelAdmin.add_form_template

12
docs/ref/contrib/gis/geoquerysets.txt
View File

@ -460,12 +460,12 @@ the values given in the given pattern. This lookup requires a tuple parameter,
MariaDB, PostGIS, and SpatiaLite
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
On these spatial backends the intersection pattern is a string comprising
nine characters, which define intersections between the interior, boundary,
and exterior of the geometry field and the lookup geometry.
The intersection pattern matrix may only use the following characters:
``1``, ``2``, ``T``, ``F``, or ``*``. This lookup type allows users to "fine tune"
a specific geometric relationship consistent with the DE-9IM model. [#fnde9im]_
On these spatial backends the intersection pattern is a string comprising nine
characters, which define intersections between the interior, boundary, and
exterior of the geometry field and the lookup geometry. The intersection
pattern matrix may only use the following characters: ``1``, ``2``, ``T``,
``F``, or ``*``. This lookup type allows users to "fine tune" a specific
geometric relationship consistent with the DE-9IM model. [#fnde9im]_
Geometry example::

13
docs/ref/contrib/gis/geos.txt
View File

@ -922,12 +922,13 @@ Prepared Geometries
===================
In order to obtain a prepared geometry, access the
:attr:`GEOSGeometry.prepared` property. Once you have a
``PreparedGeometry`` instance its spatial predicate methods, listed below,
may be used with other ``GEOSGeometry`` objects. An operation with a prepared
geometry can be orders of magnitude faster -- the more complex the geometry
that is prepared, the larger the speedup in the operation. For more information,
please consult the `GEOS wiki page on prepared geometries <https://trac.osgeo.org/geos/wiki/PreparedGeometry>`_.
:attr:`GEOSGeometry.prepared` property. Once you have a ``PreparedGeometry``
instance its spatial predicate methods, listed below, may be used with other
``GEOSGeometry`` objects. An operation with a prepared geometry can be orders
of magnitude faster -- the more complex the geometry that is prepared, the
larger the speedup in the operation. For more information, please consult the
`GEOS wiki page on prepared geometries
<https://trac.osgeo.org/geos/wiki/PreparedGeometry>`_.
For example:

7
docs/ref/contrib/gis/measure.txt
View File

@ -14,9 +14,10 @@ Specifically, it implements two objects, :class:`Distance` and
Example
=======
:class:`Distance` objects may be instantiated using a keyword argument indicating the
context of the units. In the example below, two different distance objects are
instantiated in units of kilometers (``km``) and miles (``mi``):
:class:`Distance` objects may be instantiated using a keyword argument
indicating the context of the units. In the example below, two different
distance objects are instantiated in units of kilometers (``km``) and miles
(``mi``):
.. code-block:: pycon

27
docs/ref/contrib/gis/model-api.txt
View File

@ -130,21 +130,22 @@ are not.
Most people are familiar with using latitude and longitude to reference a
location on the earth's surface. However, latitude and longitude are angles,
not distances. In other words, while the shortest path between two points on
a flat surface is a straight line, the shortest path between two points on a curved
surface (such as the earth) is an *arc* of a `great circle`__. [#fnthematic]_ Thus,
additional computation is required to obtain distances in planar units (e.g.,
kilometers and miles). Using a geographic coordinate system may introduce
complications for the developer later on. For example, SpatiaLite does not have
the capability to perform distance calculations between geometries using
geographic coordinate systems, e.g. constructing a query to find all points
within 5 miles of a county boundary stored as WGS84.
[#fndist]_
not distances. In other words, while the shortest path between two points on a
flat surface is a straight line, the shortest path between two points on a
curved surface (such as the earth) is an *arc* of a `great circle`__.
[#fnthematic]_
Thus, additional computation is required to obtain distances in planar units
(e.g., kilometers and miles). Using a geographic coordinate system may
introduce complications for the developer later on. For example, SpatiaLite
does not have the capability to perform distance calculations between
geometries using geographic coordinate systems, e.g. constructing a query to
find all points within 5 miles of a county boundary stored as WGS84. [#fndist]_
Portions of the earth's surface may projected onto a two-dimensional, or
Cartesian, plane. Projected coordinate systems are especially convenient
for region-specific applications, e.g., if you know that your database will
only cover geometries in `North Kansas`__, then you may consider using projection
Cartesian, plane. Projected coordinate systems are especially convenient for
region-specific applications, e.g., if you know that your database will only
cover geometries in `North Kansas`__, then you may consider using projection
system specific to that region. Moreover, projected coordinate systems are
defined in Cartesian units (such as meters or feet), easing distance
calculations.

8
docs/ref/forms/fields.txt
View File

@ -714,14 +714,14 @@ For each field, we describe the default widget used if you don't specify
.. attribute:: allow_files
Optional. Either ``True`` or ``False``. Default is ``True``. Specifies
whether files in the specified location should be included. Either this or
:attr:`allow_folders` must be ``True``.
whether files in the specified location should be included. Either this
or :attr:`allow_folders` must be ``True``.
.. attribute:: allow_folders
Optional. Either ``True`` or ``False``. Default is ``False``. Specifies
whether folders in the specified location should be included. Either this or
:attr:`allow_files` must be ``True``.
whether folders in the specified location should be included. Either
this or :attr:`allow_files` must be ``True``.
``FloatField``

3
docs/ref/signals.txt
View File

@ -41,7 +41,8 @@ model system.
Note also that Django stores signal handlers as weak references by default,
so if your handler is a local function, it may be garbage collected. To
prevent this, pass ``weak=False`` when you call the signal's :meth:`~django.dispatch.Signal.connect`.
prevent this, pass ``weak=False`` when you call the signal's
:meth:`~django.dispatch.Signal.connect`.
.. note::