Also remember that you can restore original handles at any time (”in case they have been overwritten with a broken object” :) ):
sys.stdout=sys.__stdout__
sys.stderr=sys.__stderr__

Regards!

import os
if os.getenv( ‘SUMATRAPATH’ ) != None :
print( “you’re in XSI” )
else:
print( “you’re not in XSI” )

Have you ever found a reliable way to know in what “environment” you’re running the code? I mean, have you found a way for the session to know if it’s taking place in command line shell or XSI?

Thanks
Bernard

I remember when the print statement used to work, without any form of wrapping, that it was a lot faster than LogMessage(). I was really missing that speed.

import time

nTime1 = time.clock()

for i in range(1000):
print ’something’

nTime2 = time.clock()
nElapsed1 = round( nTime2 - nTime1, 3 )

Application.LogMessage( nElapsed1 )

#INFO: 17.906

————————————————————

nTime3 = time.clock()

for i in range(1000):
Application.LogMessage( ’something’ )

nTime4 = time.clock()
nElapsed2 = round( nTime4 - nTime3, 3 )

#INFO: 24.488

Cheers
Bernard

This worked because their version of python was compiled with VC++ 2003 like XSI 5.1, and we re-route automatically the output of the VC++ run-time we use.

However XSI 6.0 is using the runtime of VC++ 2005 and so this has ceased to work because they are no longer using the same run-time version.

btw I”ve heard Softimage will publish a version of python for XSI on Win64 in the next few weeks…

If you figure out how to put this into a module and import it on demand, do post it. I tried and couldn”t get it to work, somehow substituting sys.stdout in the module didn”t affect my main code. Maybe I didn”t wrack my brain enough.

-Lu