Eric Snow

@vstinner has also made detailed proposals in the past and written extensively about it: * (2019) https://pythoncapi.readthedocs.io/ * (2019) https://mail.python.org/archives/list/[email protected]/thread/RNI3UUI6XUPQQNECZT2DPZFMYIJ42KZ2/ * (2019) https://mail.python.org/archives/list/[email protected]/thread/HS7WDUYFTT2MCAHQQM55UHPJLAVNYCWX/ * (2018) https://mail.python.org/archives/list/[email protected]/thread/ENRZNKIFVKK5JUELQRZKGW4WL6FYCBZ3/ * (2018) https://mail.python.org/archives/list/[email protected]/thread/IUFDUHKM2M3HHXBJWVOA2ZJUW2AEMMQI/ *...

Here's a discussion I started about having an official cython-like tool: https://mail.python.org/archives/list/[email protected]/thread/NSREULQDHSJ6SZTOY5YVSNX4U4AYJOI6/

A discussion started by @hodgestar about replacing the C-API with CFFI: https://mail.python.org/archives/list/[email protected]/thread/ZV3IQWW7XL6MHZAJARHW62WNZDCX3A4M/

@vstinner also publishes a backward-compatibility shim header that relates here: https://pythoncapi-compat.readthedocs.io/

FWIW, there has been occasional discussion about identifying an "unstable" API, which seems like it would be a distinct ring. Also, what about the difference between what extensions need vs....

@nascheme I thought the backport wouldn't apply cleanly, but here we are. Do you recall what was different about the 3.12 fix?

> @ericsnowcurrently, is this the way you'd do it in 3.12? This should be good to go. It is backport of gh-124865 + gh-125709. There shouldn't be anything particular to...

And thanks for taking the time to work on this!

In the interest of understanding what actually needs to be switched to the new lock, I ended up implementing this change separately: gh-127037. I'd be fine if we updated this...

I ended up splitting up the changes into gh-127077 and gh-127115, and credited @rruuaanng on the latter one. Let's close this PR.