p15693087
/
django
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Removed unnecessary backslashes from docs.

This commit is contained in:
Mariusz Felisiak 2019-06-20 14:04:36 +02:00 committed by GitHub
parent 7f19e37135
commit 9aeac29949
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
4 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ref/contrib/postgres/search.txt
View File

@ -38,7 +38,7 @@ To use the ``search`` lookup, ``'django.contrib.postgres'`` must be in your
``SearchVector`` ``SearchVector``
================ ================
.. class:: SearchVector(\*expressions, config=None, weight=None) .. class:: SearchVector(*expressions, config=None, weight=None)
Searching against a single field is great but rather limiting. The ``Entry`` Searching against a single field is great but rather limiting. The ``Entry``
instances we're searching belong to a ``Blog``, which has a ``tagline`` field. instances we're searching belong to a ``Blog``, which has a ``tagline`` field.

4
docs/ref/models/instances.txt
View File

@ -797,8 +797,8 @@ For example::
>>> p.get_shirt_size_display() >>> p.get_shirt_size_display()
'Large' 'Large'
.. method:: Model.get_next_by_FOO(\**kwargs) .. method:: Model.get_next_by_FOO(**kwargs)
.. method:: Model.get_previous_by_FOO(\**kwargs) .. method:: Model.get_previous_by_FOO(**kwargs)
For every :class:`~django.db.models.DateField` and For every :class:`~django.db.models.DateField` and
:class:`~django.db.models.DateTimeField` that does not have :attr:`null=True :class:`~django.db.models.DateTimeField` that does not have :attr:`null=True

4
docs/topics/auth/customizing.txt
View File

@ -727,7 +727,7 @@ providing two additional methods:
.. class:: models.CustomUserManager .. class:: models.CustomUserManager
.. method:: models.CustomUserManager.create_user(*username_field*, password=None, \**other_fields) .. method:: models.CustomUserManager.create_user(*username_field*, password=None, **other_fields)
The prototype of ``create_user()`` should accept the username field, The prototype of ``create_user()`` should accept the username field,
plus all required fields as arguments. For example, if your user model plus all required fields as arguments. For example, if your user model
@ -738,7 +738,7 @@ providing two additional methods:
# create user here # create user here
... ...
.. method:: models.CustomUserManager.create_superuser(*username_field*, password, \**other_fields) .. method:: models.CustomUserManager.create_superuser(*username_field*, password, **other_fields)
The prototype of ``create_superuser()`` should accept the username The prototype of ``create_superuser()`` should accept the username
field, plus all required fields as arguments. For example, if your user field, plus all required fields as arguments. For example, if your user

2
docs/topics/auth/default.txt
View File

@ -115,7 +115,7 @@ Changing a user's password will log out all their sessions. See
Authenticating users Authenticating users
-------------------- --------------------
.. function:: authenticate(request=None, \**credentials) .. function:: authenticate(request=None, **credentials)
Use :func:`~django.contrib.auth.authenticate()` to verify a set of Use :func:`~django.contrib.auth.authenticate()` to verify a set of
credentials. It takes credentials as keyword arguments, ``username`` and credentials. It takes credentials as keyword arguments, ``username`` and