On Thu, 7 Apr 2022, 8:02 pm Petr Viktorin, <[email protected]> wrote:
> > This applies to: > > - Functions added in PEP 523 > - PyCode_New, PyCode_NewWithPosOnlyArgs > - Ideally anything documented as subject to change between minor > releases. (To be kind to users, if something is added later we should > again have one release of compiler warnings before requiring the opt-in. > Unless that API just changed and users would get errors anyway.) > Other candidate items for this tier: * non-opaque access to frame structs and any other key APIs needed to implement alternate eval loops with comparable performance to the default eval loop (unless & until we can figure out stable public APIs that can deliver equivalent performance) > * C APIs that provide access to compiled code whether in AST or opcode form (the API itself may be stable, but the compiled code isn't, so this is kinda covered by your last point) Cheers, Nick. >
_______________________________________________ Python-Dev mailing list -- [email protected] To unsubscribe send an email to [email protected] https://mail.python.org/mailman3/lists/python-dev.python.org/ Message archived at https://mail.python.org/archives/list/[email protected]/message/CW543RWJU6EWAPTWCDDHEUS37UHSAU5I/ Code of Conduct: http://python.org/psf/codeofconduct/
