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 petr.viktorin, serhiy.storchaka
Date 2015-03-18.15:34:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1426692873.67.0.481294762765.issue23699@psf.upfronthosting.co.za>
In-reply-to
Content
Such macros would make the code cleaner. But I don't think it should be provided as a part of API. It isn't hard to implement, it doesn't provide essential functionality of Python, and it doesn't hide implementation defined CPython internals. I rather consider it as private helper, so it should be declared with underscore prefix and inside the #ifndef Py_LIMITED_API/#endif block.

I don't see an implementation of Py_RICHCOMPARE. In any case I think it would be better to make the op parameter the first parameter.
History
Date User Action Args
2015-03-18 15:34:33serhiy.storchakasetrecipients: + serhiy.storchaka, petr.viktorin
2015-03-18 15:34:33serhiy.storchakasetmessageid: <1426692873.67.0.481294762765.issue23699@psf.upfronthosting.co.za>
2015-03-18 15:34:33serhiy.storchakalinkissue23699 messages
2015-03-18 15:34:33serhiy.storchakacreate