➜

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 josh.r
Recipients benjamin.peterson, exarkun, josh.r
Date 2014-05-01.21:18:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1398979081.51.0.692137001257.issue21408@psf.upfronthosting.co.za>
In-reply-to
Content 
Why would an subclass of object that doesn't redefine either __eq__ or __ne__ have a different behavior for inequality than object itself? Bar never defined __eq__, so it shouldn't have an implicit __ne__ any more than object itself does...

Saying that Bar has an implicit __ne__ that object doesn't is answering how this happens, but it's not a why; is there a reason why this should be the case, or is this a bug (either in spec or in code) that should be fixed?
History
Date User Action Args
2014-05-01 21:18:01josh.rsetrecipients: + josh.r, exarkun, benjamin.peterson
2014-05-01 21:18:01josh.rsetmessageid: <1398979081.51.0.692137001257.issue21408@psf.upfronthosting.co.za>
2014-05-01 21:18:01josh.rlinkissue21408 messages
2014-05-01 21:18:01josh.rcreate