#29643: Hashing list in Q objects when using __in lookup
-------------------------------------+-------------------------------------
Reporter: rhyre | Owner: nobody
Type: Uncategorized | Status: new
Component: Utilities | Version: 2.0
Severity: Normal | Resolution:
Keywords: hash, tuple, list, | Triage Stage:
drf | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Description changed by rhyre:
Old description:
> When using djangorestframework with django 2.0.X with lookup __in like
> id__in=[1,2,3] will raise: unhashable type: 'list'
>
> traceback ends to this file:
> /django/utils/tree.py" in __hash__
> 74. return hash((self.__class__, self.connector, self.negated)
> + tuple(self.children))
> When using tuples with __in everything works fine. But when using
> .values_list() on query I need to use tuple(query) to use it in Q object
> with __in lookup.
> Code worked before with 1.11 version just fine. Also when using __in
> without Q() everything seems to work just fine.
New description:
When using djangorestframework with django 2.0.X with lookup _in like
{{{id__in=[1,2,3]}}} will raise: unhashable type: 'list'
traceback ends to this file:
{{{
/django/utils/tree.py" in __hash__
74. return hash((self.__class__, self.connector, self.negated) +
tuple(self.children))
}}}
When using tuples with {{{__in}}} everything works fine. But when using
.values_list() on query I need to use tuple(query) to use it in Q object
with {{{__in}}} lookup.
Code worked before with 1.11 version just fine. Also when using _in
without Q() everything seems to work just fine.
--
--
Ticket URL: <https://code.djangoproject.com/ticket/29643#comment:1>
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 [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.db2e7cbd194709d1d294d393ecbbebf6%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
