On 20/11/12 14:43, Pete O'Connell wrote:
Hi I use a compositing program called Nuke which loads my custom modules on start up. So if I have an error in my python code somewhere, Nuke won't open and it throws a typical error which is easy enough to fix. The problem I am running into is that when others on my network are using an older version of Nuke, some of my code causes their older version to not open. For example, recently I started using gnuplot.py for graphical feed back which the older version of Nuke doesn't like. So my question is:
What is the best way to wrap all my custom code so that it isn't read on startup, but rather only after I invoke a "loadMyCustomModules.py" module.
Put it in a module "loadMyCustomModules.py" instead of whatever place Nuke expects to find it. What is Nuke? What exactly does it do? Where does it expect to find your modules? What you are asking is really a question about Nuke, not Python. Can you update the other versions of Nuke? Or tell it to be more forgiving of errors? Or less aggressive about loading things automatically? -- Steven _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
