From 9aeac299490212c86952857f321812ae9df943da Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Thu, 20 Jun 2019 14:04:36 +0200 Subject: [PATCH] Removed unnecessary backslashes from docs. --- docs/ref/contrib/postgres/search.txt | 2 +- docs/ref/models/instances.txt | 4 ++-- docs/topics/auth/customizing.txt | 4 ++-- docs/topics/auth/default.txt | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/docs/ref/contrib/postgres/search.txt b/docs/ref/contrib/postgres/search.txt index d3fd5059585..026336960e5 100644 --- a/docs/ref/contrib/postgres/search.txt +++ b/docs/ref/contrib/postgres/search.txt @@ -38,7 +38,7 @@ To use the ``search`` lookup, ``'django.contrib.postgres'`` must be in your ``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`` instances we're searching belong to a ``Blog``, which has a ``tagline`` field. diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index edc4459f1c9..58557422e02 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -797,8 +797,8 @@ For example:: >>> p.get_shirt_size_display() 'Large' -.. method:: Model.get_next_by_FOO(\**kwargs) -.. method:: Model.get_previous_by_FOO(\**kwargs) +.. method:: Model.get_next_by_FOO(**kwargs) +.. method:: Model.get_previous_by_FOO(**kwargs) For every :class:`~django.db.models.DateField` and :class:`~django.db.models.DateTimeField` that does not have :attr:`null=True diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt index 282eb8ca919..007431ba33f 100644 --- a/docs/topics/auth/customizing.txt +++ b/docs/topics/auth/customizing.txt @@ -727,7 +727,7 @@ providing two additional methods: .. 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, plus all required fields as arguments. For example, if your user model @@ -738,7 +738,7 @@ providing two additional methods: # 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 field, plus all required fields as arguments. For example, if your user diff --git a/docs/topics/auth/default.txt b/docs/topics/auth/default.txt index ed546877de7..5f4c7a7a476 100644 --- a/docs/topics/auth/default.txt +++ b/docs/topics/auth/default.txt @@ -115,7 +115,7 @@ Changing a user's password will log out all their sessions. See Authenticating users -------------------- -.. function:: authenticate(request=None, \**credentials) +.. function:: authenticate(request=None, **credentials) Use :func:`~django.contrib.auth.authenticate()` to verify a set of credentials. It takes credentials as keyword arguments, ``username`` and