AWS Thinkbox Discussion Forums

Nuke Submissions error

I am testing Nuke in 10.1.16.5 but I’m getting a Python import error when trying to use the submission script:

Traceback (most recent call last):
File “C:\Users\Nick\Documents\Nuke/rt_cine_deadline\DeadlineNukeClient.py”, line 76, in main
import SubmitNukeToDeadline
File “C:\Users\Nick\Documents\Nuke/rt_cine_deadline\SubmitNukeToDeadline.py”, line 7, in
import re.Match as Match
ImportError: No module named Match

Any ideas what could be causing this? I can try and upload the repo to the latest version but it doesn’t look like there is anything in the release notes related to this.

Thanks

Nick

First off, I think this is incorrect syntax, because re is a module, not a package, so importing re.Match is wrong. from re import Match might be better.
Second, this is probably a Python 2 vs 3 issue - there is no Match class in Python 2 re.

That was also my feeling. With one of the recent release notes saying adding support for Nuke 13 I though this might by a Py2/Py3 thing.

I should also clarify, we’re using Nuke 12.2.4

This import should not be there for python 2. It is used for type annotations only, anyway.
You could surround it with a check for python 2, e.g. if six.PY2:.
I can swear I already fixed this problem somewhere, but could not find it.

I think there are more issues in it than just this though, commenting out the line that errors gets me further but I just get a new error.

Traceback (most recent call last):
File "C:\Users\Nick\Documents\Nuke/rt_cine_deadline\DeadlineNukeClient.py", line 91, in main
import SubmitNukeToDeadline
File "//***/DeadlineRepository10/submission/Nuke/Main\SubmitNukeToDeadline.py", line 38, in <module>
dialog = DeadlineDialog(-1, "", "", []) # type: DeadlineDialog # Defaulting this so mypy 
doesn't complain about incompatible types
NameError: name 'DeadlineDialog' is not defined

I guess this class is not included. Not sure where this one was coming from. You’d have to dig a bit. In the documentation there is DeadlineScriptDialog, but it might be different.

The fix is here, bit annoying that 10.1.16.8 came out without a fix for this error…

EDIT: Meant to write without not with!!!

1 Like

So it’s fixed in 10.1.16.8? We’ll just update it then, I was chasing IT to do this anyway because that is almost always the response I get when I post an error! :rofl:

Plus I should have actually searched the forum…

No, it’s not fixed in 10.1.16.8. Just upgraded from 10.1.14.x and started hitting this.

2 Likes
Privacy | Site terms | Cookie preferences