Documentation
Hello,
I want to know if the abi3-abi3t source level compatibility (not binary level compatibility) is largely done and extension authors can start compiling against 3.15.0b1 to port their source code over. I've found scant documentation on this, other than this demo repository: https://github.com/encukou/abi3-abi3t-universal/tree/b1
I have some extensions built on non-stable ABIs (3.11 and earlier) and one that's built for 3.14 (for free-threading). I want to port everything to the stable ABI, but I don't want to port to abi3 only to again have to do another port to abi3t, so I'm curious to know where things stand with abi3-abi3t and whether I can start leaping directly to it. The documentation isn't clear on this, other than just saying it's a new ABI and promoting its benefits. https://docs.python.org/3.15/whatsnew/3.15.html#whatsnew315-abi3t
I know I'll have to recompile when rc1 (or final) is out and that's okay, but I want to start the source level (C/C++ level) changes early (i.e. now) unless the devs know that source level compatibility is still in flux (like how PEP 820 changed the slot initialization).
Thanks.
Documentation
Hello,
I want to know if the abi3-abi3t source level compatibility (not binary level compatibility) is largely done and extension authors can start compiling against 3.15.0b1 to port their source code over. I've found scant documentation on this, other than this demo repository: https://github.com/encukou/abi3-abi3t-universal/tree/b1
I have some extensions built on non-stable ABIs (3.11 and earlier) and one that's built for 3.14 (for free-threading). I want to port everything to the stable ABI, but I don't want to port to abi3 only to again have to do another port to abi3t, so I'm curious to know where things stand with abi3-abi3t and whether I can start leaping directly to it. The documentation isn't clear on this, other than just saying it's a new ABI and promoting its benefits. https://docs.python.org/3.15/whatsnew/3.15.html#whatsnew315-abi3t
I know I'll have to recompile when rc1 (or final) is out and that's okay, but I want to start the source level (C/C++ level) changes early (i.e. now) unless the devs know that source level compatibility is still in flux (like how PEP 820 changed the slot initialization).
Thanks.