summaryrefslogtreecommitdiff
path: root/docs/ref/models
diff options
context:
space:
mode:
authorSaJH <wogur981208@gmail.com>2025-08-26 00:50:53 +0900
committerSarah Boyce <42296566+sarahboyce@users.noreply.github.com>2025-08-28 08:52:43 +0200
commit3c0c54351b58e9386375d2bd7a8c60dadc4bb6e8 (patch)
tree38a78ca516fc998ae29818fa7950af5278bc7c9b /docs/ref/models
parent1285de557b0b8b9c5ebe5de0114b2da5abe60f80 (diff)
Fixed #36570 -- Removed unnecessary :py domain from documentation roles.
Signed-off-by: SaJH <wogur981208@gmail.com>
Diffstat (limited to 'docs/ref/models')
-rw-r--r--docs/ref/models/expressions.txt4
-rw-r--r--docs/ref/models/fields.txt12
2 files changed, 8 insertions, 8 deletions
diff --git a/docs/ref/models/expressions.txt b/docs/ref/models/expressions.txt
index d4095a3900..121ed0f30a 100644
--- a/docs/ref/models/expressions.txt
+++ b/docs/ref/models/expressions.txt
@@ -563,7 +563,7 @@ values into their corresponding database type.
If no :ref:`output_field<output-field>` is specified, it will be inferred from
the type of the provided ``value`` for many common types. For example, passing
-an instance of :py:class:`datetime.datetime` as ``value`` defaults
+an instance of :class:`datetime.datetime` as ``value`` defaults
``output_field`` to :class:`~django.db.models.DateTimeField`.
``ExpressionWrapper()`` expressions
@@ -1094,7 +1094,7 @@ calling the appropriate methods on the wrapped expression.
Tells Django which value should be returned when the expression is used
to apply a function over an empty result set. Defaults to
- :py:data:`NotImplemented` which forces the expression to be computed on
+ :data:`NotImplemented` which forces the expression to be computed on
the database.
.. attribute:: set_returning
diff --git a/docs/ref/models/fields.txt b/docs/ref/models/fields.txt
index b08718879b..dd0862926a 100644
--- a/docs/ref/models/fields.txt
+++ b/docs/ref/models/fields.txt
@@ -1434,7 +1434,7 @@ Python native format: dictionaries, lists, strings, numbers, booleans and
.. attribute:: JSONField.encoder
- An optional :py:class:`json.JSONEncoder` subclass to serialize data types
+ An optional :class:`json.JSONEncoder` subclass to serialize data types
not supported by the standard JSON serializer (e.g. ``datetime.datetime``
or :class:`~python:uuid.UUID`). For example, you can use the
:class:`~django.core.serializers.json.DjangoJSONEncoder` class.
@@ -1443,7 +1443,7 @@ Python native format: dictionaries, lists, strings, numbers, booleans and
.. attribute:: JSONField.decoder
- An optional :py:class:`json.JSONDecoder` subclass to deserialize the value
+ An optional :class:`json.JSONDecoder` subclass to deserialize the value
retrieved from the database. The value will be in the format chosen by the
custom encoder (most often a string). Your deserialization may need to
account for the fact that you can't be certain of the input type. For
@@ -1458,7 +1458,7 @@ To query ``JSONField`` in the database, see :ref:`querying-jsonfield`.
.. admonition:: Default value
If you give the field a :attr:`~django.db.models.Field.default`, ensure
- it's a callable such as the :py:class:`dict` class or a function that
+ it's a callable such as the :class:`dict` class or a function that
returns a fresh object each time. Incorrectly using a mutable object like
``default={}`` or ``default=[]`` creates a mutable default that is shared
between all instances.
@@ -1483,8 +1483,8 @@ To query ``JSONField`` in the database, see :ref:`querying-jsonfield`.
.. admonition:: Oracle users
Oracle Database does not support storing JSON scalar values. Only JSON
- objects and arrays (represented in Python using :py:class:`dict` and
- :py:class:`list`) are supported.
+ objects and arrays (represented in Python using :class:`dict` and
+ :class:`list`) are supported.
``PositiveBigIntegerField``
---------------------------
@@ -2440,7 +2440,7 @@ Field API reference
.. attribute:: descriptor_class
- A class implementing the :py:ref:`descriptor protocol <descriptors>`
+ A class implementing the :ref:`descriptor protocol <descriptors>`
that is instantiated and assigned to the model instance attribute. The
constructor must accept a single argument, the ``Field`` instance.
Overriding this class attribute allows for customizing the get and set