This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author r.david.murray
Recipients benjamin.peterson, exarkun, josh.r, r.david.murray
Date 2014-05-01.21:47:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398980851.59.0.595676086653.issue21408@psf.upfronthosting.co.za>
In-reply-to
Content
I don't think it's a bug.  The subclass-goes-first behavior is very intentional.  The implicit __ne__ returning the boolean inverse of __eq__ is what fooled me when I looked at it.

Or did you mean that following the subclass rule in the case where object is the other class is possibly suspect?
History
Date User Action Args
2014-05-01 21:47:31r.david.murraysetrecipients: + r.david.murray, exarkun, benjamin.peterson, josh.r
2014-05-01 21:47:31r.david.murraysetmessageid: <1398980851.59.0.595676086653.issue21408@psf.upfronthosting.co.za>
2014-05-01 21:47:31r.david.murraylinkissue21408 messages
2014-05-01 21:47:31r.david.murraycreate