Source: python-pip Version: 1.5.6-2 Severity: normal Dear Maintainers,
Would it be otherwise ok to use "/usr/bin/env python3" in the shebang of /usr/bin/pip3 ? This way pip would also work directly from within an "activated" virtual environment created with --system-site-packages (i.e.: one that doesn't install it's own pip). Currently I have to call $ /path/to/venv/bin/python /usr/bin/pip3 (...) in order for it to actually notice it's being called from inside a virtual environment. Python-policy says it is "strongly preferred" to use the direct path to python in the shebang, but there's no rationale provided for this preference. Is this maybe one of the cases where it would be acceptable? Cheers -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.14-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=pt_BR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
