Workaround
Simply renaming the plugins folder which is located in C:\Program Files\Common Files\Nuke\11.2prevent Nuke from being able to locate any of your plugins and stop the error from occuring.
Reproduced by support
This bug has been reproduced in:
Nuke 11.2v1 - Windows 10
Nuke 11.1v4 - Windows 10
Nuke 11.1v1 - Windows 10
Nuke 11.0v4 - Windows 10
Nuke 11.0v1 - Windows 10
Nuke 10.5v7 - Windows 10
Nuke 10.5v1 - Windows 10
Nuke 10.0v6 - Windows 10
Nuke 10.0v1 - Windows 10 - Regression
Unable to reproduce bug in:
Nuke11.2v1 - Linux CentOS 7
Nuke 9.0v7 - Windows 10
Not tested on macOS due to Python compatibility issues.
Earliest version tested
Nuke 9.0v7
- This issue no longer appears in this version and has regressed
Expected behaviour
Nuke should be imported as a Python module with no errors.
Actual behaviour
Importing Nuke as a Python module into a third-party Python interpreter throws the following errors if you have plugins installed: