[3.2.x] Fixed typos in assertQuerysetEqual() docs and 1.6 release notes.

Backport of 0c7e880e13 from master
This commit is contained in:
Jacob Walls 2021-02-26 03:10:52 -05:00 committed by Mariusz Felisiak
parent 1c10a6cbce
commit 230d5b16b2
2 changed files with 2 additions and 2 deletions

View File

@ -165,7 +165,7 @@ Minor features
* The :meth:`~django.test.TransactionTestCase.assertQuerysetEqual` now checks * The :meth:`~django.test.TransactionTestCase.assertQuerysetEqual` now checks
for undefined order and raises :exc:`ValueError` if undefined for undefined order and raises :exc:`ValueError` if undefined
order is spotted. The order is seen as undefined if the given ``QuerySet`` order is spotted. The order is seen as undefined if the given ``QuerySet``
isn't ordered and there are more than one ordered values to compare against. isn't ordered and there is more than one ordered value to compare against.
* Added :meth:`~django.db.models.query.QuerySet.earliest` for symmetry with * Added :meth:`~django.db.models.query.QuerySet.earliest` for symmetry with
:meth:`~django.db.models.query.QuerySet.latest`. :meth:`~django.db.models.query.QuerySet.latest`.

View File

@ -1695,7 +1695,7 @@ your test suite.
provide an implicit ordering, you can set the ``ordered`` parameter to provide an implicit ordering, you can set the ``ordered`` parameter to
``False``, which turns the comparison into a ``collections.Counter`` comparison. ``False``, which turns the comparison into a ``collections.Counter`` comparison.
If the order is undefined (if the given ``qs`` isn't ordered and the If the order is undefined (if the given ``qs`` isn't ordered and the
comparison is against more than one ordered values), a ``ValueError`` is comparison is against more than one ordered value), a ``ValueError`` is
raised. raised.
Output in case of error can be customized with the ``msg`` argument. Output in case of error can be customized with the ``msg`` argument.