Matthieu Darbois

Thanks for the explanation of your stat. Indeed 99% of systems not manylinux2010 compliant systems are not compliant only because of `pip`. > many of whom have no idea about...

> In your data, you can see CentOS 7 and Ubuntu 18.04 clearly listed with pip 9 yes > there’s also a mystery 2.26 distro with pip 9. `glibc 2.26`...

> Seeing Python version there could also be interesting. I dropped the patch version on everything not to get too many rows. https://docs.google.com/spreadsheets/d/1ZV-xf-2qXkPUdPp8D8i4qRq6Jo1GSNlJQBGuLyVkiGQ/edit?usp=sharing ``` SELECT t0.cpu, t0.num_downloads, t0.python_version, t0.pip_version, t0.glibc_version...

Thanks @henryiii for those. The end of support date planned is after CPython 3.6 EOL. The plan might be revisited depending on the evolution of statistics (Edit: added those to...

@cbrnr, > I have no idea what's up with those automatically generated manylinux1 wheels. This is the behavior of `auditwheel=4` in https://github.com/pypa/auditwheel/pull/289 (1 wheel but still would mention manylinux1 compatibility...

The active support for manylinux1 is now over. Given the time supporting the image has dropped considerably with update automation, I don't see a reason why actually stopping those updates....

@ax3l, unfortunately I don't. you can try to run `auditwheel show` or run in verbose mode to see if this helps. PR are welcomed for this issue.

While this would work in simple environments but there's nothing that enforces the 2 packages to live in the same `site-packages` folder. e.g. in the following extract, all 3 packages...

> On second thought, maybe in @rgommer's scheme no support is required from auditwheel, since the loading done by import pkg_with_sharedlib will not be noticed by auditwheel. even with @rgommers...

OK, I guess something like: ``` pkg_with_sharedlib |- __init__.py |- _init.abi3.so |- sharedlib.so.1 ``` with `__init__.py` just being `import ._init` and `_init.c` having a call into `sharedlib.so.1` in its `PyInit__init`...