No, I kept it a good old normal command. So changes to the actual command .py
file do update immediately... unlike with a self installed plugin in which I
would have to reload it. Its the modules referenced from the command .py file
with an import statement that are not updating.
-brad
Quoting kim aldis <kim(at)aldis.org.uk>:
> How is the command built, through a self-installing plugin?
>
> > -----Original Message-----
> > From: owner-xsi(at)Softimage.COM
> > [mailto:owner-xsi(at)Softimage.COM] On Behalf Of xsibrad(at)fie.us
> > Sent: 20 July 2005 22:24
> > To: xsi(at)Softimage.COM
> > Subject: simply python modules question
> >
> > Hi,
> >
> > I've got a command that's importing a custom python module.
> >
> > I've added the package to the PYTHONPATH variable and it runs.
> >
> > However, if I open the module, make a change, and save it, I
> > have to restart XSI in order for the change to make it into
> > the XSI execution environment.
> >
> > Is there a well known and accepted way to have the XSI python
> > execution evironment flush the module from memory and reload
> > it from the new source without having to restart XSI?
> >
> > Before I spend hours trying to work around this myself, I
> > thought I'd check with the minds on the list. I'm fairly new
> > to Python.
> >
> > Thanks.
> >
> > -brad
> >
> >
> >
> > ----------------------------------------------------------------
> > 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
>
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
