 | | | XSI Python error log | XSI Python error log 2004-04-26 - By Jerry Gamache
Back
Hello Christian,
Python is supported via the ActiveScripting interface provided by the win32all
package (now called PyWin32). This package is as dynamically developped as XSI
and sometimes small changes in win32all can cause our scripting code to fail by
basically exposing some unexpected way we talk to the ActiveScripting interface
.
I spent some time installing multiple versions of Python and win32all so I can
say that for XSI version 3.5.1 you should use Python version 2.2.3 with
win32all version 148.
Locations:
Python 2.2.3: http://www.python.org/2.2.3/
more specifically: http://www.python.org/ftp/python/2.2.3/Python-2 (See http://hon-2.ora-code.com).2.3.exe
win32all 148: http://starship.python.net/crew/mhammond/win32/Downloads.html
more specifically: http://starship.python.net/crew/mhammond/downloads/win32all
-148.exe
The errors first appeared in win32all 150.
For XSI 4.0, we corrected these issues and you should be able to use more
recent versions of Python and win32all.
If someone intends to use both versions of XSI in parallel, they can put a call
to the proper version of pyscript.py in the XSI startup batch file to update
the registry before the application starts.
i.e.:
@(protected) off
rem XSI 3.5.1 Startup batch file
rem Set ActiveScripting to use Python 2.2.3 and win32all 148:
C:\Python22\Lib\site-packages\win32comext\axscript\client\pyscript.py
@(protected) Now we can start XSI:
call C:\Softimage\XSI_3.5.1\Application\bin\setenv.bat
start "" C:\Softimage\XSI_3.5.1\Application\bin\xsi.exe %1 %2 %3 %4 %5 %6 %7 %8
%9
Hope this helps.
Jerry.
-- --Original Message-- --
From: owner-xsi@(protected) [mailto:owner-xsi@(protected)]On Behalf
Of Christian Rittener
Posted At: Monday, April 26, 2004 3:58 PM
Posted To: xsi
Conversation: XSI Python error log
Subject: Re: XSI Python error log
Sorry to disagree, but right now I'd say they make it almost unusable in XSI
3.5.1. If I make a mistake in a one-line script, how am supposed to find
what I did wrong among the dozens of error messages that scroll by, only one
of which is really related to my mistake?
And I thought Python was truly supported since the beginning (or at least
v.2.0) ! Nobody ever mentioned this, neither was mentioned the need to hack
into the language... I just don't understand. And that script to make XSI
constants available, suddenly falling from the sky (no offence Jerry, thanks
for your efforts)... Has nobody needed this until now ? are these problems
fixed in V.4 ?
Please Python users out there, speak out.
Christian Rittener
> The errors are annoying but do not prevent Python scripting from
> working.
---
Unsubscribe? Mail Majordomo@(protected) with the following text in body:
unsubscribe xsi
|
|
|