Problem summary
Nuke errors when closing when a deleted EXR type Write node has a Knob Changed callback. The error it produces is:
Traceback (most recent call last): File "C:/Program Files/Nuke10.0v3/plugins\nuke\callbacks.py", line 127, in knobChanged _doCallbacks(knobChangeds) File "C:/Program Files/Nuke10.0v3/plugins\nuke\callbacks.py", line 46, in _doCallbacks f[0](*f[1],**f[2]) File "C:/Users/peter.coleman/.nuke/init.py", line 3, in printNode print nuke.thisNode()ValueError: A PythonObject is not attached to a node
Customer reported version
nuke.10.0v2
Customer reported platform
n_a_linux
Steps to reproduce
1) Place the attached init.oy into your .nuke folder
2) Open Nuke via command line
3) Create a Write node
4) Change the file type to exr
5) Delete the Write node
6) Close Nuke, the command window will show the error.
This only effects the exr format and only if the Write node has been deleted.
Reproduced by support
This is a regression.
The issue has been reproduced on:
Nuke 10.0v3 - Windows 10
Nuke 10.0v1 - Windows 10 - CentOS 6.7
Nuke 9.0v8 - Windows 10 - CentOS 6.7
Nuke 9.0v1 - Windows 10
The bug was not present on:
Nuke 8.0v6 - Windows 10 - CentOS 6.7
Nuke 8.0v1 - Windows 10
Nuke 7.0v10 - Windows 10
Expected behaviour
No error messages when Nuke closed
Actual behaviour
The error messages appeared