#19652: Fix for #19524 introduced a backward compatiblity issue with related
managers on 1.5.X
-------------------------------------+-------------------------------------
Reporter: charettes | Owner: charettes
Type: Bug | Status: closed
Component: ORM aggregation | Version:
Severity: Release blocker | 1.5-beta-1
Keywords: none EmptyQuerySet | Resolution: fixed
none | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Aymeric Augustin <aymeric.augustin@…>):
In [changeset:"9328ef0e84db2559af56d24c40e6b24b74e29a6f"]:
{{{
#!CommitTicketReference repository=""
revision="9328ef0e84db2559af56d24c40e6b24b74e29a6f"
[1.5.x] Avoided a possible regression in 5097d3c5.
QuerySet.none() returns an instance of EmptyQuerySet, which may have
undesirable side effects in the presence of custom query set classes.
The implementation of .none() was refactored in master to have the same
effect as .filter(pk__in=[]).
Refs #19652.
Thanks Simon Charrette for the report.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/19652#comment:13>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit https://groups.google.com/groups/opt_out.
