Re: linux: PYTHONPATH env var and XSI

[Nick Fowler <nfowler(at)mainframe.ca>]

At Mainframe we add this to the .xsi file:
setenv PYTHONPATH   "${XSI_BINDIR}:${PYTHONPATH}:/mainframe/.../..../.../i386/lib/python2.3/site-packages"
# above needs explicit site packages path since PYTHONHOME setting below
#  screws up the prefix_dir handling - thanks softimage!
setenv PYTHONHOME   "$XSI_BINDIR"

Nick Fowler

Subject:

linux: PYTHONPATH env var and XSI

From:

"Greg Smith" <greg(at)stanwinston.com>

Date:

Wed, 12 Apr 2006 10:03:16 -0700

Okay got a linux question regarding python and XSI, more particularly =
using the enviroment variable PYTHONPATH. Now I am aware that XSI ships =
with Python 2.3 and a version of pywin32. Which pretty much makes it =
independent from the install on Linux itself. However for some reason, =
python library in XSI does not look at the PYTHONPATH environment =
variable. Is there a reason for this?  I figured out how to get around =
this by executing the following script in the script editor, but =
personally I think its a band-aid solution and not a proper resolve:

import sys
sys.path.ammend('python path variable')

I am curious if there is something that I need to set first in order for =
"" to work. And on another note, what if I wanted to use a more recent =
build of Python instead of the one included with XSI? am I SOL? =20



------------------------------
  

--- Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body: unsubscribe xsi