Does uv honor the no-manylinux install flags?

[harmstyler]

PIP honors a flag for disabling the use of manylinux pre-built whl files. When I use uv and the no-manylinux package, my build finishes in seconds (yay), but that makes me think that uv is not building the manylinux whl files itself, as my normal pip install takes an hour.

https://peps.python.org/pep-0600/ https://github.com/asottile-archive/no-manylinux/blob/main/_manylinux.py

What? Why? The manylinux spec requires compliant packages to vendor binary dependencies inside the wheel that is distributed. Take for example a library which would (prior to manylinux) dynamically link against libssl. As libssl received security patches, the system binaries would received updates from the OS's package manager. The python library which dynamically links would receive these updates for free without need to recompile, reinstall, etc. Under manylinux, libssl is vendored inside the wheel. To receive security updates, you have to wait for the upstream to produce a new wheel and need to know to install a new version of that library. There's almost no visibility about these vendored wheels which makes managing them at scale impossible. As such, some may choose to ignore this standard.