Hi all and Happy New Year!
I've noticed something very strange while debugging a script and I thought I'd
bounce it off the group...
If I run the following to load a script in interactive mode in the terminal:
nuke -t myBuggyScript.nk
Error messages print out *** and then it EXITS back to shell prompt...
However, if I start an interactive session first, and then open the script, by
running:
nuke -t
nuke.scriptOpen("myBuggyScript.nk")
Identical error messages print out ***BUT THEN the interactive prompt stays
OPEN so I can do whatever I need to the script -- as expected.
The reason this is an issue is because I ultimately want to process my Nuke
script with a python script via command line; i.e.:
nuke -t myPythonScript.py myBuggyScript.nk
And I'm noticing when I use 'nuke.scriptOpen("myBuggyScript.nk")' from within
the Python script, it too just exits back out to the shell and ignores all
subsequent python commands in myPythonScript.py.
Obviously, it's not good to have errors in my script -- nevertheless, I should
be able to get the exact same behavior that allows me to continue working on
the script whether opening it via python or command line -- just as I do when
launching Nuke interactively, and then opening the script.
Is this a known issue? Anyone have an idea how I can work around this?
Cheers,
Jep_______________________________________________
Nuke-python mailing list
Nuke-python@support.thefoundry.co.uk, http://forums.thefoundry.co.uk/
http://support.thefoundry.co.uk/cgi-bin/mailman/listinfo/nuke-python
