On Mon, Nov 19, 2012 at 10:43 PM, Pete O'Connell <pedrooconn...@gmail.com> 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.
I found the following in the docs: http://docs.thefoundry.co.uk/nuke/63/pythondevguide/startup.html Can you add your plugins via ~/.nuke/init.py? _______________________________________________ Tutor maillist - Tutor@python.org To unsubscribe or change subscription options: http://mail.python.org/mailman/listinfo/tutor
