so Finally I get to reply. So I did what you suggest about copying the
files over from /usr/lib/python2.3/site-packages/
to /usr/Softimage/XSI_6.02/Application/bin/lib/python2.3/site-packages/,
that pretty much did the trick, and since the part that was compiled was
already built and I had .so file from the same linux environment that I
am running in, it posed no problems. I found out there was a site
package that was an extension to the xml module that tends to override
the standard xml module for python which works fine outside of XSI, but
breaks it within. So looks like I'm back in action! thanks for the
reply!
On Fri, 2007-08-03 at 15:33 -0400, Patrick Boucher wrote:
> I've delt with Python & Linux but never XSI, Python and Linux so I'm
> shooting from the hip as I truly have no idea how much special sauce there
> is in the XSI Python build.
>
> As most add-on packages that live in the /usr/lib/python2.3/site-packages
> are only location agnostic folders and files and could be pretty much
> anywhere on the filesystem, it would be nice to try to copy your custom
> module (PyXml or MySQLdb) from your local install to the XSI install's
> site-packages.
>
> A lot of modules are python only so they should work no problem within a
> special Python's such as XSI's.
>
> If a custom package has a compiled part to it (C++, which MySQLdb surely
> has) then it might be trickier. Try a simple copy first but you might have
> to go the extra step of building from source against XSI's Python but I'm
> not even sure you'd have what you need to do that. You'd probably need at
> least the XSI Python header files to get that to work.
>
> The radio silence you were getting is definitely because this is a tricky
> one and you might be treading new territory...
>
> Cheers,
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
