Author serhiy.storchaka
Recipients lemburg, mark.dickinson, methane, rhettinger, serhiy.storchaka, vstinner
Date 2017-02-15.10:01:05
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1487152866.1.0.191846884499.issue29548@psf.upfronthosting.co.za>
In-reply-to
Content
I think first at all PyEval_Call* functions should be documented (issue11165). The documentation should recommend to use corresponding PyObject_Call* functions and explicitly describe the difference between PyEval_Call* and PyObject_Call* APIs.

Few releases after deprecating PyEval_Call APIs in documentation we can add the Py_DEPRECATED attribute for emitting compiler warnings. Few releases after deprecating in code we can remove PyEval_Call* declarations from headers, but keep exporting them in binary library. In Python 4 (or other major release that will break binary compatibility) they can be removed at all.
History
Date User Action Args
2017-02-15 10:01:06serhiy.storchakasetrecipients: + serhiy.storchaka, lemburg, rhettinger, mark.dickinson, vstinner, methane
2017-02-15 10:01:06serhiy.storchakasetmessageid: <1487152866.1.0.191846884499.issue29548@psf.upfronthosting.co.za>
2017-02-15 10:01:06serhiy.storchakalinkissue29548 messages
2017-02-15 10:01:05serhiy.storchakacreate