Jim Langston wrote:
> I think it's because your python directory is in the path before your
> python2.5 directory.
Thanks for the tip. In fact, /usr/local/bin/python (2.5) is on my PATH
before /usr/bin/python (2.3).
I did find the problem however -- it turns out that caching the executable
path
"Jeffrey Froman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello All,
>
> I have two python versions installed, one in /usr/bin, and one in
> /usr/local/bin. However, when invoking python without a full path,
> I get the wrong executable with the right sys.executable string!
>
"Jeffrey Froman" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hello All,
>
> I have two python versions installed, one in /usr/bin, and one in
> /usr/local/bin. However, when invoking python without a full path,
> I get the wrong executable with the right sys.executable string!
>
Hello All,
I have two python versions installed, one in /usr/bin, and one in
/usr/local/bin. However, when invoking python without a full path,
I get the wrong executable with the right sys.executable string!
[EMAIL PROTE
