Message 287769 - Python tracker

➜

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	methane
Recipients	lemburg, mark.dickinson, methane, serhiy.storchaka, vstinner
Date	2017-02-14.11:37:38
SpamBayes Score	-1.0
Marked as misclassified	Yes
Message-id	<1487072258.2.0.603655547954.issue29548@psf.upfronthosting.co.za>
In-reply-to

Content
> I would suggest to deprecate PyEval_Call*() functions first only in the documentation. In 3.8 or 3.9 add the Py_DEPRECATED attribute. <Include/ceval.h> doesn't excluded by PEP 384. And these 3 functions and 1 macro is outside of "#ifndef Py_LIMITED_API" check. So they are part of stable ABI. We can't remove them until Python 4. No reason to hurry up. I'll remove Py_DEPRECATED for Python 3.7.

> I would suggest to deprecate PyEval_Call*() functions first only in the documentation. In 3.8 or 3.9 add the Py_DEPRECATED attribute.


<Include/ceval.h> doesn't excluded by PEP 384.
And these 3 functions and 1 macro is outside of "#ifndef Py_LIMITED_API" check.
So they are part of stable ABI.  We can't remove them until Python 4.
No reason to hurry up.

I'll remove Py_DEPRECATED for Python 3.7.

History
Date	User	Action	Args
2017-02-14 11:37:38	methane	set	recipients: + methane, lemburg, mark.dickinson, vstinner, serhiy.storchaka
2017-02-14 11:37:38	methane	set	messageid: <1487072258.2.0.603655547954.issue29548@psf.upfronthosting.co.za>
2017-02-14 11:37:38	methane	link	issue29548 messages
2017-02-14 11:37:38	methane	create