[3.1.x] Fixed typos in assertQuerysetEqual() docs and 1.6 release notes.
Backport of 0c7e880e13
from master
This commit is contained in:
parent
bdad3eb7ec
commit
200b71b593
|
@ -165,7 +165,7 @@ Minor features
|
|||
* The :meth:`~django.test.TransactionTestCase.assertQuerysetEqual` now checks
|
||||
for undefined order and raises :exc:`ValueError` if undefined
|
||||
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
|
||||
:meth:`~django.db.models.query.QuerySet.latest`.
|
||||
|
|
|
@ -1665,7 +1665,7 @@ your test suite.
|
|||
provide an implicit ordering, you can set the ``ordered`` parameter to
|
||||
``False``, which turns the comparison into a ``collections.Counter`` comparison.
|
||||
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.
|
||||
|
||||
Output in case of error can be customized with the ``msg`` argument.
|
||||
|
|
Loading…
Reference in New Issue