I believe this is very premature. Aside from a handful of hand-curated packages where highly capable people contributed that support, we basically have no degree of broader roll-out in the ecosystem. As a very concrete example, we’re still waiting for a free-threading-compatible release of Cython, which underlies a large number of very popular packages. People have been using alpha versions or commits from main so far, but we really haven’t gotten broad usage here.
x2
In conda-forge, we believe that we’ll be able to start the migration for free-threading build in conda-forge sometime this spring – this will likely surface a large amount of issues. I had been keen to start this process earlier, but other people more deeply involved with the free-threading effort told me at the time that this was premature. As such, I’m quite surprised to see this proposal already.
Overall, I also think that the problems can be fixed, but on an ecosystem-level (i.e. outside of CPython) we’ve really only barely started to find out the impact of this. Given the following quote from the acceptance of PEP 703 (my bold)
we’re really not there yet. Sam et al. cannot clone themselves to support nogil builds for all projects across the ecosystem, so IMO we need the community to be able to handle this independently of the nogil luminaries, before we can talk about “enough community support”.