RE: [script] Same python code, different results

Date : Mon, 15 Aug 2005 14:49:07 -0400
To : <XSI(at)Softimage.COM>
From : "Andrew Skowronski" <askowron(at)Softimage.COM>
Subject : RE: [script] Same python code, different results
Having some out-of-date script files in memory is a good theory - 
XSI caches a self-installed plug-in script in 
memory once it is first instantiated. 

So in Kim's scenario the Logmessage won't actually show up until

-XSI restarted
-Update button on Plug-in Manager pressed
-Some OM code called to unload/reload the specific plugins

-Andrew

-----Original Message-----
From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM]On Behalf
Of kim aldis
Posted At: Monday, August 15, 2005 12:17 PM
Posted To: xsi
Conversation: [script] Same python code, different results
Subject: RE: [script] Same python code, different results


 try taking the plugins you think everyone is using, add a coded logmessage
in the init or command, wait for a baddy and see if the log is there, or
check see if everyone gets the log.

> -----Original Message-----
> From: owner-xsi(at)Softimage.COM 
> [mailto:owner-xsi(at)Softimage.COM] On Behalf Of Bernard Lebel
> Sent: 15 August 2005 17:08
> To: XSI(at)Softimage.COM
> Subject: Re: [script] Same python code, different results
> 
> Here the issues affects self-installed commands, not imported 
> libraries. Isn't the command names garbaged collected 
> immediately after it returns?
> 
> Bernard
> 
> 
> On 8/15/05, xsibrad(at)fie.us <xsibrad(at)fie.us> wrote:
> > I have been noticing some oddities on our python setup as well... 
> > though nothing as large as what you seem to be running into.
> > 
> > Since I never removed the LogMessage commands from some of our self 
> > installed python commands (ir lazy), I do get to see when they init 
> > and all that jazz (hey, we're still in developoment... not 
> release).  
> > and often a python self installed command will fail to init 
> once and then init fine the next time...
> > with no changes to its code.  So far it has not caused any 
> major problems.
> > Except of course the problem of confusing and belittling 
> the programmer (me).
> > 
> > I guess the next obvious question is: has this been 
> happening during a 
> > period that you've been coding into your python tools?  Is 
> it possible 
> > that a module has been loaded into the python runtime for 
> like... two 
> > days... since some artists may leave XSI running that long? 
>  In that 
> > time, you could have updated the code twice... but they 
> might still have the old version loaded into memory.
> >  Or is that a wild goose chase too?  I thought I'd point out the 
> > obvious easy solutions first.  Cause the next suggestion becomes 
> > testing out different python installs (activestate vs. 
> python.org etc).  ouch.
> > 
> > -brad
> > 
> > Quoting Bernard Lebel <3dbernard(at)gmail.com>:
> > 
> > > Andrew:
> > >
> > > >> Maybe there is a command conflict (same command name
> > >
> > > I'm pretty sure that is not the case! I mean, otherwise, wouldn't 
> > > all of the 25 users of the workgroup run into these 
> problems? I seem 
> > > to never run into these problems (or almost), while some 
> others run 
> > > into this several times a day.
> > >
> > > >> or command scripting name being used more than once)?
> > >
> > > Hum I will 100ple-check that, thanks for the tip.
> > >
> > >
> > >
> > > Kim:
> > >
> > > > Sounds to me like some of the machines are looking at older 
> > > > versions of code?
> > >
> > > That is extremely unlikely. The reason is the only plugin the 
> > > Plugins directory in the workgroup contains is a plugin 
> loader, it 
> > > explicitely load plugin files that are located in a directory not 
> > > part of the workgroup. Unless the plugin loader has duplicate 
> > > entries, loading plugins of the same name twice is 
> technically impossible.
> > >
> > > But again I will 101ple-check all this stuff. Thanks for the tip.
> > >
> > >
> > >
> > > Bernard
> > >
> > > ---
> > > Unsubscribe? Mail Majordomo(at)Softimage.COM with the 
> following text in body:
> > > unsubscribe xsi
> > >
> > 
> > 
> > 
> > 
> > ----------------------------------------------------------------
> > This message was sent using IMP, the Internet Messaging Program.
> > 
> > ---
> > Unsubscribe? Mail Majordomo(at)Softimage.COM with the 
> following text in body:
> > unsubscribe xsi
> >
> 
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following 
> text in body:
> unsubscribe xsi
> 

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

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


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.