#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
-------------------------------------+-------------------------------------
Comment (by Carlton Gibson):
Hi. Thanks for the follow-up.
This still isn’t really a minimal reproduce.
Can you provide a test-case that demonstrates the issue? Or a small
project?
Any chance you could use git bisect to identify the commit which broke
your usage?
> Without DRF it seems to work just fine. There is a problem with
serialization
What exactly do you mean here? It’s not quite clear. (Do you mean that the
ORM call works fine until embedded with the DRF request-response handling?
If so you’ll need to provide a sample project I think…(?))
Could you paste the entire traceback for the error?
--
Ticket URL: <https://code.djangoproject.com/ticket/29643#comment:4>
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/063.e81ec5084606641861c136df25670381%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
