Unfortunately, that's not my call at the moment. I'm working on my argument and this discussion is great fodder. Ah, OK. I didn't realize the situation was out of your control, so once again, sorry for all the noise. I was under the impression you had been tasked with improving the general workflow as you saw fit.
For the remaining hack-and-paste contributors, the project based init scripts are at their disposal. The project context switching is still going to happen through our in-app project switcher. Based on this sort of an approach, and since you're interested in using deferred init.py/menu.py files to keep things familiar for the contributors, exec or execfile() are probably the best options. What you would probably want to do is something similar to what Rich mentioned: When you get to the point that you want to bootstrap the project environment, try-except the execution of the configuration scripts, and display information on any exceptions as necessary. You would probably also want to make the execution of any menu.py files contingent on the successful execution of a corresponding init.py from the same directory (if one exists). -Nathan
_______________________________________________ Nuke-python mailing list [email protected], http://forums.thefoundry.co.uk/ http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
