#28629: Q objects are no longer hashable in 2.0.
-------------------------------------+-------------------------------------
Reporter: coady | Owner: felixxm
Type: Bug | Status: closed
Component: Database layer | Version: 2.0
(models, ORM) |
Severity: Release blocker | Resolution: fixed
Keywords: Q hash | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"8368d5a4006d84abacbcf53b9688a8f84ccf6f0c" 8368d5a4]:
{{{
#!CommitTicketReference repository=""
revision="8368d5a4006d84abacbcf53b9688a8f84ccf6f0c"
[2.0.x] Fixed #28629 -- Made tree.Node instances hashable.
Regression in 508b5debfb16843a8443ebac82c1fb91f15da687 which
added Node.__eq__().
Backport of fc6528b25ab1834be1a478b405bf8f7ec5cf860c from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28629#comment:5>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/063.719da5728d46b95aea77d5bb625a3656%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
