#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
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

 * status:  assigned => closed
 * resolution:   => fixed


Comment:

 In [changeset:"fc6528b25ab1834be1a478b405bf8f7ec5cf860c" fc6528b]:
 {{{
 #!CommitTicketReference repository=""
 revision="fc6528b25ab1834be1a478b405bf8f7ec5cf860c"
 Fixed #28629 -- Made tree.Node instances hashable.

 Regression in 508b5debfb16843a8443ebac82c1fb91f15da687 which
 added Node.__eq__().
 }}}

-- 
Ticket URL: <https://code.djangoproject.com/ticket/28629#comment:4>
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.6b4dec9adc818df5edbb44d6d0c24677%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to