This is up for grabs.

For reference, the Steering Council approved getting rid of these two C APIs without honoring the customary two-release deprecation period required by PEP 387.

For reference see https://github.com/python/steering-council/issues/75. This also has references to python-dev and python-committers discussions.

PS. It would be nice to also update Cython, which is the only thing that uses these C APIs.

If possible, I suggest to do in in this order:

* Fix Cython
* Publish a Cython release including the fix
* (Maybe wait a bit)
* Remove the two functions

Previously, we tried to first modified Python, and then update Cython: it went bad.

Otherwise, the following 136 popular PyPI packages will fail to build on Python 3.11:
https://mail.python.org/archives/list/python-dev@python.org/message/6RO2WFU5Q7UQDVL72IRMT4T6L4GEAKB6/

In Fedora, we start to integrate Python 3.11 since alpha 1. In the past, the broken Cython was really annoying: many important packages failed to build, and so everything was broken. Hopefully, we can now patch Cython, and we modified most recipes building Python packages to always regenerate Cython source, to avoid such problem.

I understood that these function calls shoud be replaced with:

* PyCode_NewEmpty(const char *filename, const char *funcname, int firstlineno)
* code.replace() method: https://docs.python.org/dev/library/types.html#types.CodeType.replace

That sounds like a good plan (note that alpha 1 will go out around Oct 4).

I left an issue for Cython: https://github.com/cython/cython/issues/4365

FYI, mypyc is using PyCode_New.
mypyc should be fixed not to use PyCode_New :)

I sent the patch for this issue: https://github.com/python/mypy/pull/11067

Nuitka (https://github.com/Nuitka/Nuitka/ - a third Python->C API compiler) also looks to use it so you might want to let them know too while you're doing the rounds on this.

Da-woods, can you take care of that?

Done: https://github.com/Nuitka/Nuitka/issues/1203