➜

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 gvanrossum
Recipients Dennis Sweeney, Guido.van.Rossum, Mark.Shannon, Yonatan Goldschmidt, ammar2, chris.jerdonek, corona10, erlendaasland, gvanrossum, hauntsaninja, pablogsal, petr.viktorin, rhettinger, scoder, serhiy.storchaka, vstinner
Date 2021-08-13.14:24:33
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1628864673.24.0.637318290574.issue40222@roundup.psfhosted.org>
In-reply-to
Content 
> >> I want to get rid of PyCode_NewWithPosArgs() and just have PyCode_New(). 

> That as added because of PEP 387 and unfortunately removing it is backwards incompatible.

Is changing the signature allowed? Because it *must* be changed (at the very least to accommodate the exceptiontable, but there are several others too -- your PEP 657 touched it last to add endlinetable and columntable).

I think this was a mistake in PEP 387 and we just need to retract that. Perhaps it could be left as a dummy that always returns an error?

> >> I propose we declare all APIs for code objects *unstable*, liable to change each (feature) release.

> I agree that we should do this, but this needs at least a discussion in python-dev because currently these APIs are protected by PEP 387 so changing them is backwards incompatible

Yeah that's the crux. :-(
History
Date User Action Args
2021-08-13 14:24:33gvanrossumsetrecipients: + gvanrossum, rhettinger, scoder, vstinner, petr.viktorin, chris.jerdonek, Mark.Shannon, serhiy.storchaka, Guido.van.Rossum, ammar2, corona10, pablogsal, Dennis Sweeney, erlendaasland, Yonatan Goldschmidt, hauntsaninja
2021-08-13 14:24:33gvanrossumsetmessageid: <1628864673.24.0.637318290574.issue40222@roundup.psfhosted.org>
2021-08-13 14:24:33gvanrossumlinkissue40222 messages
2021-08-13 14:24:33gvanrossumcreate