mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-03-12 10:22:37 +00:00
Code Issues 32 Releases Wiki Activity

Tweaked docs to avoid reformatting given new black version.

Browse Source
This commit is contained in:
nessita 2025-01-30 10:37:14 -03:00 committed by GitHub
parent cbb0812683
commit fd3cfd80be
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/ref/contrib/postgres/aggregates.txt
View File

@ -51,11 +51,10 @@ General-purpose aggregation functions
Examples::
"some_field"
"-some_field"
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())
.. deprecated:: 5.2

12
docs/releases/1.10.txt
View File

@ -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
hardware. To make Django users acknowledge continued use of weak hashers, the
following hashers are removed from the default :setting:`PASSWORD_HASHERS`
setting::
setting:
"django.contrib.auth.hashers.SHA1PasswordHasher"
"django.contrib.auth.hashers.MD5PasswordHasher"
"django.contrib.auth.hashers.UnsaltedSHA1PasswordHasher"
"django.contrib.auth.hashers.UnsaltedMD5PasswordHasher"
"django.contrib.auth.hashers.CryptPasswordHasher"
* ``"django.contrib.auth.hashers.SHA1PasswordHasher"``
* ``"django.contrib.auth.hashers.MD5PasswordHasher"``
* ``"django.contrib.auth.hashers.UnsaltedSHA1PasswordHasher"``
* ``"django.contrib.auth.hashers.UnsaltedMD5PasswordHasher"``
* ``"django.contrib.auth.hashers.CryptPasswordHasher"``
Consider using a :ref:`wrapped password hasher <wrapping-password-hashers>` to
strengthen the hashes in your database. If that's not feasible, add the