Open ngoldbaum opened 1 month ago
Our C extension is built with mypyc, so I'd prefer a solution inside mypyc rather than something special we do ourselves.
Until mypyc supports free-threading, users using free-threading should be able to use our pure-Python wheel; I don't think mypyc even supports 3.13 with the GIL yet.
Also, the tests you flag depend on aiohttp; I wonder if the failures are because aiohttp doesn't support free-threading yet.
I see 3.13 support is being tracked over at https://github.com/mypyc/mypyc/issues/1056.
Is your feature request related to a problem? Please describe.
It looks like everything is mostly working on the free-threaded build, except for three failing tests:
This is with a version of black I built using the free-threaded build of Python3.13.0rc1. I ran the tests with
PYTHON_GIL=0
to force the GIL to be disabled. I also built aiohttp with an updated version of cython (see https://github.com/aio-libs/aiohttp/issues/8796).You should be able to follow https://py-free-threading.github.io/porting/ to declare that C extensions support running without the GIL, assuming there are no known or suspected thread safety issues.
Describe the solution you'd like
Supporting free-threaded Python without any special hacking.