[0] https://groups.google.com/forum/?#!msg/django-
developers/wdO0e0835EY/X_D9gVe_EwAJ
--
Ticket URL: <https://code.djangoproject.com/ticket/31235>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* stage: Unreviewed => Accepted
Comment:
I think the suggested approach makes sense, I suggest we deprecate the
`repr` default entirely through a deprecation period.
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:1>
* status: new => assigned
* needs_better_patch: 0 => 1
* version: 3.0 => master
* owner: nobody => Peter Inglesby
* has_patch: 0 => 1
Comment:
[https://github.com/django/django/pull/12417 PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:2>
* owner: Peter Inglesby => Hasan Ramezani
* needs_better_patch: 1 => 0
Comment:
[https://github.com/django/django/pull/13557 New PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:3>
* needs_better_patch: 0 => 1
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:4>
Comment (by Hasan Ramezani):
Mariusz:
I rebased the PR and changed a lot of assertions and remove `repr` from
`assertQuerysetEqual`.
There are some assertions that are using `repr`. most of them are for
models that use more than one field in `__str__`.
like:
* https://github.com/django/django/pull/13557/files#diff-
ad6ec549eed244cc16532a3944710bfee97faeba6e3d21fbea58a5cb544254d2R1013
* https://github.com/django/django/pull/13557/files#diff-
ad3486daf49a0018f6d9202fbdaf3392dda74e2543decf9bdc43f37d2ebec8b2R221
I think we can keep them as is. what do you think?
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:5>
* needs_better_patch: 1 => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:6>
* stage: Accepted => Ready for checkin
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:7>
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"3f7b3275627385f8f7531fca01cdda50d4ec6b6e" 3f7b327]:
{{{
#!CommitTicketReference repository=""
revision="3f7b3275627385f8f7531fca01cdda50d4ec6b6e"
Fixed #31235 -- Made assertQuerysetEqual() compare querysets directly.
This also replaces assertQuerysetEqual() to
assertSequenceEqual()/assertCountEqual() where appropriate.
Co-authored-by: Peter Inglesby <peter.i...@gmail.com>
Co-authored-by: Mariusz Felisiak <felisiak...@gmail.com>
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:8>
Comment (by GitHub <noreply@…>):
In [changeset:"bc43ae7c13b903022ec1fcb4867f5f10d7f125d6" bc43ae7]:
{{{
#!CommitTicketReference repository=""
revision="bc43ae7c13b903022ec1fcb4867f5f10d7f125d6"
Refs #31235 -- Improved assertQuerysetEqual() warning message with
stacklevel=2.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:9>
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"104d6172e85101658147a568de86bb678fa1c019" 104d6172]:
{{{
#!CommitTicketReference repository=""
revision="104d6172e85101658147a568de86bb678fa1c019"
[3.2.x] Refs #31235 -- Improved assertQuerysetEqual() warning message with
stacklevel=2.
Backport of bc43ae7c13b903022ec1fcb4867f5f10d7f125d6 from main
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:10>
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"e2be307b3ab6ebf339b3a765fe64967c9602266f" e2be307]:
{{{
#!CommitTicketReference repository=""
revision="e2be307b3ab6ebf339b3a765fe64967c9602266f"
Refs #31235 -- Made assertQuerysetEqual() not call repr() on a queryset
when compared to string values.
Per deprecation timeline.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31235#comment:11>