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 serhiy.storchaka
Recipients David Seddon, abarry, ncoghlan, rhettinger, serhiy.storchaka
Date 2015-11-28.11:19:50
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1448709591.17.0.309006060046.issue25732@psf.upfronthosting.co.za>
In-reply-to
Content
This doesn't work with new-style classes that always have __ne__ inherited from object.

I afraid that the only way to fix this issue is to backport Python 3 behavior of default __ne__, automatically fallback to __eq__.
History
Date User Action Args
2015-11-28 11:19:51serhiy.storchakasetrecipients: + serhiy.storchaka, rhettinger, ncoghlan, abarry, David Seddon
2015-11-28 11:19:51serhiy.storchakasetmessageid: <1448709591.17.0.309006060046.issue25732@psf.upfronthosting.co.za>
2015-11-28 11:19:51serhiy.storchakalinkissue25732 messages
2015-11-28 11:19:51serhiy.storchakacreate