Matthieu Darbois

> delocate provides similar functionality for macOS, perhaps it would worth collaborating with @matthew-brett for better multi-platform support. I meant `x86_64` vs `aarch64` rather than `linux` vs `macOS` which is...

@zackw, I was looking into including `libcrypt.so.1` from `libxcrypt` in addition to `libcrypt.so.2` in the manylinux images (and development dependencies for the latter). It seems `libcrypt.so.1` also exports all symbols...

The newly merged PR should allow to graft `libcrypt.so.1`. I'm keeping this issue opened as a reminder that `libxcrypt` will (soon ?) provide both shared object with 1 build which...

> Travis returned "The job exceeded the maximum time limit for jobs, and has been terminated." This was just a glitch. I triggered a build on travis-ci without any cache...

Thanks @marcelotduarte !

Hello @thomaslima, First, I'm no security expert so the following is just my 2 cents. As mentioned in the KLayout issue, if relying on system packages, in the end, those...

Another option not mentioned in the previous comment would be to update from `manylinux2014` to `manylinux_2_24` or the upcoming `manylinux_2_28` (if they're not impacted). This would come with its own...

> Let me know if I can provide any clarification on this PR. A bit of background on the real use-case would be nice since it seems to differ from...

@henryiii, > the reason 99% users get manylinux1 is not glibc version Can you provide the source of this stat ? The stats in the linked [comment](https://github.com/pypa/manylinux/issues/542#issuecomment-720139926) suggested less than...

I updated the stats by looking at February downloads on PyPI: ``` SELECT t0.cpu, t0.num_downloads, t0.pip_version, t0.glibc_version FROM (SELECT COUNT(*) AS num_downloads, details.installer.version AS pip_version, details.distro.libc.version AS glibc_version, details.cpu FROM...