On Wed, Oct 31, 2001 at 02:04:05AM -0800, Chuck Esterbrook wrote:
> It also
> doesn't help that Debian is so far behind the current version of Python.
It's not behind. python2 was forked into a separate package for
political reasons. Namely, the former GPL-compatibility brou-ha-ha.
Python 1.5.
[EMAIL PROTECTED] wrote:
>
>Pretty much all the Webware and 3rd party plug-ins invoke the Python
>interpreter by calling "#!/usr/bin/env python" in their scripts. The
>trouble with this is that this call brings up Python 1.5.2 in Debian.
Only if you have the path to Python 1.5.2 before the path t
At 02:19 AM 10/31/2001 -0500, [EMAIL PROTECTED] wrote:
>Pretty much all the Webware and 3rd party plug-ins invoke the Python
>interpreter by calling "#!/usr/bin/env python" in their scripts. The
>trouble with this is that this call brings up Python 1.5.2 in Debian.
>
>The only ways I can think of
Well, I switched "python" to 2.0 some time ago on Debian, and I've had
very few problems (pysol is the only one I can remember).
Of course, I'm sure there are packages I don't use that do cause these
problems.
A general "change the first line of everything" script would probably
be useful anyway
Pretty much all the Webware and 3rd party plug-ins invoke the Python
interpreter by calling "#!/usr/bin/env python" in their scripts. The
trouble with this is that this call brings up Python 1.5.2 in Debian.
The only ways I can think of to get Python 2 invoked instead is to use the
Debian alterna
