#29503: Order of parameters pass to __in lookup affected by de-duplication.
-------------------------------------+-------------------------------------
Reporter: Nick Pope | Owner: Nick Pope
Type: Bug | Status: assigned
Component: Database layer | Version: 1.11
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Carlton Gibson):
* cc: Carlton Gibson (added)
* stage: Unreviewed => Ready for checkin
Comment:
I'd be happy with the use of `OrderedSet` here. Semantically `in` uses a
set but we (always/mostly?) pass it a list, which is ordered, and it's
reasonable enough to maintain that. (Beyond Nick's usage, it could be
handy somewhere.)
Is this a regression? Was it always part of the contract? Not sure. Pass.
:)
--
Ticket URL: <https://code.djangoproject.com/ticket/29503#comment:5>
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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/065.19c62f224578a26ce1f5cae8120ee90e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
