mirror of
https://github.com/django/django.git
synced 2025-04-01 12:06:43 +00:00
[5.1.x] Tweaked docs to avoid reformatting given new black version.
Backport of fd3cfd80bebad292d639a03e58632e494369eb92 from main.
This commit is contained in:
parent
9d1945df8f
commit
4f0169e94f
@ -49,11 +49,10 @@ General-purpose aggregation functions
|
|||||||
|
|
||||||
Examples::
|
Examples::
|
||||||
|
|
||||||
"some_field"
|
|
||||||
"-some_field"
|
|
||||||
from django.db.models import F
|
from django.db.models import F
|
||||||
|
|
||||||
F("some_field").desc()
|
ArrayAgg("a_field", order_by="-some_field")
|
||||||
|
ArrayAgg("a_field", order_by=F("some_field").desc())
|
||||||
|
|
||||||
.. versionchanged:: 5.0
|
.. versionchanged:: 5.0
|
||||||
|
|
||||||
|
@ -687,13 +687,13 @@ If you have an old Django project with MD5 or SHA1 (even salted) encoded
|
|||||||
passwords, be aware that these can be cracked fairly easily with today's
|
passwords, be aware that these can be cracked fairly easily with today's
|
||||||
hardware. To make Django users acknowledge continued use of weak hashers, the
|
hardware. To make Django users acknowledge continued use of weak hashers, the
|
||||||
following hashers are removed from the default :setting:`PASSWORD_HASHERS`
|
following hashers are removed from the default :setting:`PASSWORD_HASHERS`
|
||||||
setting::
|
setting:
|
||||||
|
|
||||||
"django.contrib.auth.hashers.SHA1PasswordHasher"
|
* ``"django.contrib.auth.hashers.SHA1PasswordHasher"``
|
||||||
"django.contrib.auth.hashers.MD5PasswordHasher"
|
* ``"django.contrib.auth.hashers.MD5PasswordHasher"``
|
||||||
"django.contrib.auth.hashers.UnsaltedSHA1PasswordHasher"
|
* ``"django.contrib.auth.hashers.UnsaltedSHA1PasswordHasher"``
|
||||||
"django.contrib.auth.hashers.UnsaltedMD5PasswordHasher"
|
* ``"django.contrib.auth.hashers.UnsaltedMD5PasswordHasher"``
|
||||||
"django.contrib.auth.hashers.CryptPasswordHasher"
|
* ``"django.contrib.auth.hashers.CryptPasswordHasher"``
|
||||||
|
|
||||||
Consider using a :ref:`wrapped password hasher <wrapping-password-hashers>` to
|
Consider using a :ref:`wrapped password hasher <wrapping-password-hashers>` to
|
||||||
strengthen the hashes in your database. If that's not feasible, add the
|
strengthen the hashes in your database. If that's not feasible, add the
|
||||||
|
Loading…
x
Reference in New Issue
Block a user