On 15 July 2017 at 17:44, Nathaniel Smith <n...@pobox.com> wrote: > On Fri, Jul 14, 2017 at 10:51 PM, Nick Coghlan <ncogh...@gmail.com> wrote: > I guess that's... sort of true? But it seems to me that the goal > should be that Python shouldn't be finding broken packages on its > search path, and AFAICT there are only two ways to accomplish that: > > - give Pythons with different SOABIs different search paths > - mandate that *all* wheels be "multi-SOABI" wheel files that include > every possible SOABI > > Installing a single-SOABI wheel into a multi-SOABI search path is just > asking for trouble.
Not really - it just means that that particular package will break if the SOABI doesn't match. The only way to avoid that outcome is to run a fully isolated virtualenv that can't see *either* of the system site-packages directories and hence has its own copy of everything it needs. > Also AFAICT PyPy also shares the same --user path as the corresponding > CPython release, so this isn't just restricted to debug builds of > Python. Sure, and that's why __pycache__ works the way it does. So Ned's probably right that we need to provide written guidance that single-SOABI wheels implicitly assume the use of virtual environments to handle parallel installation, so if you want to fully support system and user level installations (rather than leaving that problem to redistributors), you'll need multi-SOABI wheel files that include all the necessary binaries in one archive. Cheers, Nick. -- Nick Coghlan | ncogh...@gmail.com | Brisbane, Australia _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
