#30971: Query.resolve_lookup_value coerces value of type list to tuple
-------------------------------------+-------------------------------------
Reporter: George Marshall | Owner: George
| Marshall
Type: Bug | Status: closed
Component: Database layer | Version: 3.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
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 Mariusz Felisiak <felisiak.mariusz@…>):
* status: assigned => closed
* resolution: => fixed
Comment:
In [changeset:"fa6076daf460df2c2c5ff9f62862f050bc4427f4" fa6076da]:
{{{
#!CommitTicketReference repository=""
revision="fa6076daf460df2c2c5ff9f62862f050bc4427f4"
[3.0.x] Fixed #30971 -- Prevented Query.resolve_lookup_value() from
coercing list values to tuples.
Regression in 8a281aa7fe76a9da2284f943964a9413697cff1f.
Backport of 8be79984dce7d819879a6e594ca69c5f95a08378 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/30971#comment:8>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.1078eb369e52d52645d3a11f754d0e8f%40djangoproject.com.
