On Jan 2, 2:28 pm, John Machin wrote:
> On Jan 3, 1:09 am, "Kelly, Brian" wrote:> After
> following your suggestions I was able to confirm that the 2.5
> > interpreter was being invoked. So then I grepped for all instances of python
> > in the scripts that were imported as modules: from bacula_c
On Jan 3, 1:09 am, "Kelly, Brian" wrote:
> After following your suggestions I was able to confirm that the 2.5
> interpreter was being invoked. So then I grepped for all instances of python
> in the scripts that were imported as modules: from bacula_conf import *
>
> The calling script cleanup.py
cember 30, 2008 4:42 PM
To: python-list@python.org
Subject: Re: python import sys.path
On Dec 31, 5:05 am, "Kelly, Brian" wrote:
> I have both 2.4 and 2.5 interpreters installed on a linux box. The
> PythonPath is set to :
>
>
PYTHONPATH=/usr/lib64/portage/pym:/prod/bacula/loc
On Dec 31, 5:05 am, "Kelly, Brian" wrote:
> I have both 2.4 and 2.5 interpreters installed on a linux box. The
> PythonPath is set to :
>
> PYTHONPATH=/usr/lib64/portage/pym:/prod/bacula/local/lib64/python2.4/site-pa
> ckages:/prod/bacula/local/lib/python2.4/site-packages
>
> My main script is get
I have both 2.4 and 2.5 interpreters installed on a linux box. The
PythonPath is set to :
PYTHONPATH=/usr/lib64/portage/pym:/prod/bacula/local/lib64/python2.4/site-pa
ckages:/prod/bacula/local/lib/python2.4/site-packages
My main script is getting called like so:
python2.4 cleanup.py wrkstnbs
Th