Over in #834193, a user is asking for a /usr/bin/pip2 to mirror /usr/bin/pip because some uses cases apparently prefer pip2 over pip. That seems like a reasonable request on the face of it, and easy to support.
However, I thought, well why not shebang pip2 to /usr/bin/python2 because 1)
it would parallel the script name; 2) I do think it would be in our best long
term interest to start shebanging system scripts explicitly with python3 or
python2 as appropriate. Yes, I know that we don't intend to make
/usr/bin/python be Python 3 any time soon, but maybe someday we'll change our
minds and PEP 394 will embrace that strategy across Linux distros.
In any case, it produces a mild lintian complaint:
E: python-pip: python-script-but-no-python-dep usr/bin/pip2
Of course the /usr/bin/python shebanged /usr/bin/pip doesn't produce that
warning, and the package's Depends properly has ${python:Depends}. I think
lintian is wrong, but I'd like to hear any other opinions.
Cheers,
-Barry
pgpa5POdfuIrO.pgp
Description: OpenPGP digital signature
