Joe Rickerby

> The only case affected is projects trying to build EoL Python version with python requires set via setup.py will suddenly not get those old wheels, and will have to...

Yeah, that seems right to me, but I'd be inclined to prefix on the cpython ones, just to be explicit. ``` cpython-free-threading cpython-prerelease pypy graalpy ``` Just in case we...

> Couldn't we just require both if that happens? For example, if there was a pypy prerelease, it could be `["pypy", "prerelease"]`? You are basically opting-in, saying you know these...

I just checked the [official decision](https://github.com/python/steering-council/issues/221#issuecomment-1841593283) on this and it looks like`cpython-freethreading` is the way to go.

Possibly the same issue as #308. This might be an architectural change to the call stack renderer, so unlikely to be a quick fix. But if anyone hits this and...

I think due to the complexity involved, that's unlikely to be a feature that we offer. Each package can contain its own pyproject.toml, so we'd have to somehow combine the...

I wonder, why do the venvs _not_ add this. Seems a little odd. But I'd be open to adding a symlink to our venvs on macOS if others are hitting...

Closing, regarding the initial question - isolated builds are to be expected. To disable build isolation you can use the [build-frontend](https://cibuildwheel.pypa.io/en/stable/options/#build-frontend) setting, e.g. ```toml build-frontend = { name = "build",...

I've already written code to install a version of python-build-standalone in #2002, along with version pinning etc. I think it would work nicely here too.

I'm trying this out locally on pyinstrument. Building works, but I'm hitting an error running tests. Here's the output log ``` Testing wheel... + python -c 'import sysconfig; print(sysconfig.get_platform(), end="")'...