On Tue, 2020-07-21 at 14:24 -0700, David Mathog wrote:
On Tue, Jul 21, 2020 at 2:03 PM Filipe Laíns <lains@archlinux.org> wrote:
On Tue, 2020-07-21 at 13:51 -0700, David Mathog wrote:
biopython-1.77, for instance, when installed into a virtualenv with pip3, has many of these shebangs:
#!/usr/bin/env python
Is it being installed as an egg or wheel? Can you check what happens when you pass --use-pep517 to the pip install command (to force installing as a wheel)?
It is wheel, it creates a directory
biopython/lib/python3.6/site-packages/biopython-1.77.dist-info
when installed either of these ways:
pip3 install biopython pip3 install biopython --use-pep517
Either way it has the same shebang in the files listed a few posts up.
Thanks,
David Mathog
You've fallen off-list again. The shebang handling for wheels is very well defined[1]. It looks like those shebangs come from biopython so it's their bug. No file a python package is supposed to be executed directly, so they shouldn't really have shebangs. The files that are superposed to be executed directly should be defined as scripts and have a #!python shebang so that the wheel installer can do its job properly. So unfortunately I think in most of the packages you are having issues with, the bug comes from the package upstream :/ [1] https://www.python.org/dev/peps/pep-0427/#recommended-installer-features Filipe Laíns