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 rhettinger
Recipients Jim.Jewett, catalin.iacob, codemiller, eric.araujo, francescor, javawizard, lregebro, ncoghlan, python-dev, rhettinger
Date 2013-07-11.07:10:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
After more thought, I'm changing this to Py3.4 only.  For prior versions, I'm content to document that there is no support for NotImplemented, and if that is needed, then people should write-out all six rich comparisons without using the total ordering decorator.

I don't think it is a good idea to introduce the new behaviors into otherwise stable point releases.  This patch is somewhat complex and has potential for bugs, unexpected behaviors, misunderstandings, and intra-version compatability issues (like the problems that occurred when True and False were added in a point release many years ago).
Date User Action Args
2013-07-11 07:10:21rhettingersetrecipients: + rhettinger, ncoghlan, eric.araujo, lregebro, francescor, catalin.iacob, python-dev, javawizard, Jim.Jewett, codemiller
2013-07-11 07:10:21rhettingersetmessageid: <>
2013-07-11 07:10:21rhettingerlinkissue10042 messages
2013-07-11 07:10:21rhettingercreate