#34104: Making Q.__eq__ work regardless of ordering
-------------------------------------+-------------------------------------
Reporter: Daniel Wysocki | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 4.1
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: query | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* type: Uncategorized => New feature
* resolution: => needsinfo
Comment:
Thanks for the report. The main question is: why do you need to change the
current behavior? Is it problematic for Django itself? Please provide a
rationale.
--
Ticket URL: <https://code.djangoproject.com/ticket/34104#comment:2>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070183ec94fa12-5b1c8aee-db79-4993-a525-3d3c7b6c7078-000000%40eu-central-1.amazonses.com.
