#36934: BuiltinLookup breaks with params-as-a-tuple in django 6.0
-------------------------------------+-------------------------------------
Reporter: Stefan Bühler | Owner: (none)
Type: Bug | Status: closed
Component: Database layer | Version: 6.0
(models, ORM) |
Severity: Release blocker | Resolution: needsinfo
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* resolution: => needsinfo
* status: new => closed
Comment:
Hi, thanks for the report, and thanks Clifford for triage. Clifford, I
don't know if you saw the closely related #36922, which we closed since it
was the responsibility of the custom lookup to return params in a tuple.
We chose not to backport since this should only be an issue if you've
subclassed the lookups and added further customizations. Your link doesn't
go to a custom lookup, so I can't tell how you're affected. Could you
please include a stacktrace and the custom lookup?
We have to weigh the potential upside from backporting against the
downside of introducing unexpected problems in projects that already
tested against the 6.0 betas. Eager to see the fuller stacktrace & lookup,
and we can look again at that point. Thanks.
--
Ticket URL: <https://code.djangoproject.com/ticket/36934#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 [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019c7610c7d7-acf944f3-9f2b-4640-99eb-44fb03610e9d-000000%40eu-central-1.amazonses.com.
