Ben Darnell

It looks like this has been done. The docs in question have been moved to https://cibuildwheel.pypa.io/en/stable/platforms/#what-to-provide and no longer have the warnings about "when Pip 20.3 is common".

Looks like the only error on ubuntu is the musllinux one which doesn't look like our fault. That's good, but not too surprising because our use of threads is minimal...

That looks related to the new [context_aware_warnings](https://docs.python.org/3.14/whatsnew/3.14.html#free-threaded-mode) flag. It looks like the context is now being captured earlier than expected. I'm a little surprised that this is the only problem...

> Context is somehow not propagated correctly. It's not that context is propagating incorrectly, it's that modifying a contextvar is semantically different from modifying global variables. We just need to...

> As far as I understand, this should be opaque to user code and catch_warnings, simplefilter and friends should continue to behave the same (at least in single-threaded code). So...

No, I don't have any near-term plans for the next release. The existing release works fine for free-threading, right? You just have to build the extension from source.

I would also tend to go region-by-region, although I don't think it makes a lot of difference and I'm mainly basing this on the fact that orchestration tooling is more...

I'm also unsure of my policy for setuptools versions; I've never really had to think about it. Now that we can put a version in the build-system section of pyproject.toml...

In https://github.com/tornadoweb/tornado/pull/3433 I've removed the `bdist_wheel` override entirely after verifying that it doesn't break anything.

Oh dear, that `print` was a mistake. But otherwise, this was a deliberate change. Why should requests that fail to conform to the RFCs be accepted? Sometimes there's a good...