Your message dated Sat, 9 Aug 2014 16:58:31 +0100
with message-id
<CAB4XWXwVJO=Y2HSB48LtBT_bwP3kfkNsLxHeJt=eVi04uc=g...@mail.gmail.com>
and subject line Re: [Python-apps-team] Bug#527473: pylint: refers to global
python interpreter
has caused the Debian Bug report #527473,
regarding pylint: refers to global python interpreter
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
527473: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527473
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: pylint
Version: 0.14.0-2.2
Severity: wishlist
pylint refers to `/usr/bin/python' in its shebang line. It would be nice
if it could use `/usr/bin/env python' instead, to run under the Python
interpreter the user wants. Use case: if you have a private instance
created with python-virtualenv you really don't want to run the global
interpreter but the one in your path to find all the libraries in use.
--- End Message ---
--- Begin Message ---
> The prefered way to do this at Logilab is using
>
> /explicit/path/to/mypython /usr/bin/pylint arguments
>
> after having set the PYTHONPATH appropriately if required. This is done for
> example to test a module against python2.4.
upstream author provided the preferred solution they use, hence closing the bug.
Regards,
--
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi
--- End Message ---
