Thanks, at least now I know I wasn't doing something wrong.
Marc 'BlackJack' Rintsch wrote:
> In <[EMAIL PROTECTED]>, veracon wrote:
>
> > Actually, it appears to still be using the default binary
> > (/usr/bin/python). Can I be sure it's actually reading the .profile
> > file? I'm executing throu
In <[EMAIL PROTECTED]>, veracon wrote:
> Actually, it appears to still be using the default binary
> (/usr/bin/python). Can I be sure it's actually reading the .profile
> file? I'm executing through regular CGI in Apache.
The `~/.profile` is executed when *you* log into your account. CGI
scripts
Actually, it appears to still be using the default binary
(/usr/bin/python). Can I be sure it's actually reading the .profile
file? I'm executing through regular CGI in Apache.
veracon wrote:
> Thanks a lot!
>
> Jerry wrote:
> > /usr/bin/env just searches your PATH variable to find it, but it does
Thanks a lot!
Jerry wrote:
> /usr/bin/env just searches your PATH variable to find it, but it does
> so in order. So, if you want it to find your python instead of a
> system provided one, just alter your PATH variable and put
> /home/my_username/python2.5 in front of everything else.
>
> example
/usr/bin/env just searches your PATH variable to find it, but it does
so in order. So, if you want it to find your python instead of a
system provided one, just alter your PATH variable and put
/home/my_username/python2.5 in front of everything else.
example in .profile:
PATH=/home//python2.5:$P
Long story short, in order to use Python 2.5, I've compiled it in my
own account on my hosting. It works fantastic as
/home/my_username/python2.5, but the shebang is a bit long. Is there a
way to shorten it (environment variables?) or, even better, make
/usr/bin/env python point to it?
Thanks in a
