On Jul 15, 2017, at 01:51, Nick Coghlan <ncogh...@gmail.com> wrote: > Well, sort of - it's not intrinsic to *pip* or *Python* that this > happens, it's an artifact of the fact that even though the > compatibility tagging scheme allows for it, folks don't tend to > publish "multi-SOABI" wheel files (where the 35dm and 35m binaries are > in the same wheel), so installing one will uninstall the other.
Right, which is why I asserted it's a packager's problem. > Rather than attempting to change how site-packages works (which > wouldn't help until 3.7+ anyway), the main missing piece in the status > quo is the equivalent of a "mergewheel" operation that creates those > multi-SOABI files and thus allows both sets of binaries to be added to > the same environment (the same way Linux distros do for the system > site-packages directory). Without thinking too much about it, perhaps another option would be for packagers to provide two wheels: one containing all files needed for the non-debug case and a second wheel that only contains the debug extension modules (with their usual unique fila names) and that depends on the first wheel. In any case, I agree that this isn't something that has come up often in the past but perhaps some best practices should be documented in the packaging user guide. I added a comment to that effect in open issue #284: https://github.com/pypa/python-packaging-user-guide/issues/284 -- Ned Deily n...@python.org -- [] _______________________________________________ Distutils-SIG maillist - Distutils-SIG@python.org https://mail.python.org/mailman/listinfo/distutils-sig
