Henry Schreiner

Okay, I'll change > I don't think that's a big problem to lose 18.04 when we already had to give up CentOS 7. to "I think it's a good idea"....

Ahh, cross compiling was a reason to use 2_24 over manylinux2014, forgot about that (since you are generally stuck with the system compilers when cross compiling). But 2_28 is better...

The wheels still work, so I'd not worry about legacy setup.py's too much. Guessing a few distro packaging systems might like it, but other than that, it's probably not useful.

https://pypi.org/project/installer/, I assume. Designed to allow distributions and such to use pure-python wheels instead of SDists?

Probably need more info. Build does work on Windows. Are you sure the extensions are missing (not just looking at them in Explorer, which can hide extensions), do you have...

Could you try increasing the path length limit? https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#maximum-path-length-limitation Classifiers don't affect things, they are just metadata. The build is happening in a temporary directory, so the location of the...

It shouldn't strip all variables, that would be a disaster. Currently the only way to communicate options to the build backend is via environment variables (especially important for binary build...

Ahh, though you are interested in the environment during the pip download. Thought that should still be controllable via environment variables, things like `PIP_PREFER_BINARY` and such work there.

First, I'd have to ask: are you sure you want to change it? The "correct" way is to produce a `linux` wheel, then to give it to `auditwheel`, which will...

What are you trying to target? `manylinux_2_17_x86_64` (`manylinux2014`) or `manylinux_2_5_x86_64` (`manylinux1`)? It looks like you are building a valid `manylinux2014` wheel and trying to repair it down to `manylinux1`. You...