➜

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 martin.panter
Recipients benjamin.peterson, exarkun, flox, josh.r, martin.panter, r.david.murray
Date 2015-01-11.00:29:01
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1420936141.12.0.339051333798.issue21408@psf.upfronthosting.co.za>
In-reply-to
Content 
There is a bit of analysis of the object.__ne__() implementation in Issue 4395. If my understanding is correct, I think it is a bug that object.__ne__(self, other) evaluates “not self == other”. It should evaluate “not self.__eq__(other)” instead, so that NotImplemented can be caught, allowing the reflected other.__ne__(self) method to be tried.
History
Date User Action Args
2015-01-11 00:29:01martin.pantersetrecipients: + martin.panter, exarkun, benjamin.peterson, r.david.murray, flox, josh.r
2015-01-11 00:29:01martin.pantersetmessageid: <1420936141.12.0.339051333798.issue21408@psf.upfronthosting.co.za>
2015-01-11 00:29:01martin.panterlinkissue21408 messages
2015-01-11 00:29:01martin.pantercreate