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 petr.viktorin
Recipients ethan.furman, petr.viktorin, serhiy.storchaka, skrah
Date 2015-03-20.12:43:30
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
Serhiy: Thanks for looking at this!
I think it should fall in the same category as Py_RETURN_TRUE or Py_RETURN_NONE. Sure, it's easy to reimplement, but a lot of extensions need it; why should everyone need to write the same code in a dozen different ways?
I specifically want this usable in third-party code.

The implementation of Py_RICHCOMPARE is in the first patch. The second is example use.
The signature mirrors richcmpfunc. Why would op be better as first argument?

Stefan: Which optimizer should I look at? Is it important to generate the same code? 

Sorry if I'm asking for something obvious, I'm not a regular here.
Date User Action Args
2015-03-20 12:43:31petr.viktorinsetrecipients: + petr.viktorin, skrah, ethan.furman, serhiy.storchaka
2015-03-20 12:43:30petr.viktorinsetmessageid: <>
2015-03-20 12:43:30petr.viktorinlinkissue23699 messages
2015-03-20 12:43:30petr.viktorincreate