#31122: Clarify how the Lookup class follow the Query Expression API.
-------------------------------------+-------------------------------------
Reporter: Hongtao Ma | Owner: Caio
Type: | Ariede
Cleanup/optimization | Status: closed
Component: Documentation | Version: 3.0
Severity: Normal | 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
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"7ace6265d68febc2914aafe39cd671c13da43715" 7ace6265]:
{{{
#!CommitTicketReference repository=""
revision="7ace6265d68febc2914aafe39cd671c13da43715"
[3.1.x] Fixed #31122 -- Clarified that Lookup acts as a query expression.
Backport of 9a3454f6046b9b7591fd03e21cf6da0b23c57689 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/31122#comment:10>
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.9055fdd6ba1725b550eca3428a8d0b32%40djangoproject.com.
