On Thu, 2003-09-11 at 13:32, Kenneth Pronovici wrote:
[...]
> Actually, the kicker is, pychecker isn't a Python script - it's a shell
> script (condensed below):
[...]
Using a script like this to pick which version of python to use seems
wierd to me... it doesn't have much benefits over just using
> for this scheme, you don't need to make /usr/bin/pychecker handle
> alternate python versions explicitly. Just put '#!/usr/bin/python' at
> the front, and the correct /usr/lib/pythonX.Y will be on the pythonpath.
> If they explicitly use a different python version by running;
>
> $ python2.1 /us
On Thu, 2003-09-11 at 05:06, Kenneth Pronovici wrote:
> Hi,
>
> I've taken over the pychecker package from Arto Jantunen, and I'm
> looking over the remaining bugs. One of the three is #137320:
>
>http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=137320
>
> It requests that the Pychecker mo
Hi,
I've taken over the pychecker package from Arto Jantunen, and I'm
looking over the remaining bugs. One of the three is #137320:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=137320
It requests that the Pychecker modules be installed in the Python search
path, so they can be imported,
4 matches
Mail list logo
