Generating import library for Python 3.13t free-threaded DLL

[davidhewitt]

I think we might need a separate python313t.def as well as generation options for the free-threaded build.

My reason for thinking this: symbols like PyUnstable_Module_SetGIL, which PyO3 does use, are only defined on the free-threaded build.

So I think we correspondingly might need to specifically generate a free-threaded import library? I'll try to find an example which doesn't work with the current setup.

[ravenexp]

Makes sense. I'll try to figure out if the GitHub actions we use support co-installing 3.13 and 3.13t at the same time.

[davidhewitt]

Awesome, thanks!

You might be interested in using https://github.com/Quansight-Labs/setup-python

Not sure about co installing but that fork does accept 3.13t as an install option.

[ravenexp]

You might be interested in using https://github.com/Quansight-Labs/setup-python

Not sure about co installing but that fork does accept 3.13t as an install option.

Thanks for the pointer. Microsoft support is being funny as always.

[ravenexp]

The implementation is done, but I'd like someone to look at the new public API before updating the documentation.
Are stringly-typed ABI tags such as "t" good enough or would an enum be more convenient to use in pyo3-build? @davidhewitt