Message287834
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. |
|
Date |
User |
Action |
Args |
2017-02-15 10:01:06 | serhiy.storchaka | set | recipients:
+ serhiy.storchaka, lemburg, rhettinger, mark.dickinson, vstinner, methane |
2017-02-15 10:01:06 | serhiy.storchaka | set | messageid: <1487152866.1.0.191846884499.issue29548@psf.upfronthosting.co.za> |
2017-02-15 10:01:06 | serhiy.storchaka | link | issue29548 messages |
2017-02-15 10:01:05 | serhiy.storchaka | create | |
|