AWS Thinkbox Discussion Forums

Module Could Not be Found

[code]>>> import sys

draftPath = r"C:\Program Files\Thinkbox\Deadline\bin\Draft\64bit"
sys.path.append(draftPath)
sys.path
[’’, ‘C:\Python27\Lib\idlelib’, ‘C:\Windows\system32\python27.zip’, ‘C:\Python27\DLLs’, ‘C:\Python27\lib’, ‘C:\Python27\lib\plat-win’, ‘C:\Python27\lib\lib-tk’, ‘C:\Python27’, ‘C:\Python27\lib\site-packages’, ‘C:\Program Files\Thinkbox\Deadline\bin\Draft\64bit’]

import Draft

Traceback (most recent call last):
File “<pyshell#20>”, line 1, in
import Draft
ImportError: DLL load failed: The specified module could not be found.[/code]

I’m getting this error now that I updated to the latest draft build. I wasn’t getting this before. I thought it was because I was pointing directly at a remote file server so I overwrote my local copy and tried importing from there and same error. Any ideas?

Do you have MAGICK_CONFIGURE_PATH set? (I’m not 100% sure this is the problem, but check that it points to your draft build.)

Cheers,
Andrea

Edited: forgot the k (again!) in MAGICK_CONFIGURE_PATH .

I didn’t have a sys variable for that. I added it but it didn’t help. I tried both the local and network path.

EDIT: I also checked my license server. I had one expired set of 10 draft licenses and one permanent working 25 license entry so I deleted the expired one but that also didn’t change anything.

  1. Which version of Python are you running? (I normally use 2.6, but I notice most of your paths are using 2.7… not sure if that would make a difference.)
  2. I forgot the ‘K’ in MAGICK_CONFIGURE_PATH (again).
  3. If you cd to the directory that contains the draft build, can you import Draft there?

Cheers,
Andrea

Python 2.7.3 (default, Apr 10 2012, 23:24:47) [MSC v.1500 64 bit (AMD64)] on win32

import sys; sys.path.append(r"C:\Program Files\Thinkbox\Deadline\bin\Draft\64bit");import Draft

Tried with the new system variables (again local and network) no change.

Tried with Python 2.6 and that worked. So it’s a Python 2.7 incompatibility.

Thanks for figuring that out. When Paul is back, I’ll check with him to see if the Python 2.7 incompatibility is known or not, and what the intention for compatibility is. You were previously able to use Python 2.7?

Cheers,
Andrea

Maybe not. I haven’t been keeping very good track and I got a new computer so I might have just gone with a new version when I upgraded without thinking.

Ah. I’m familiar with that. :wink: Anyway, are you okay with using Python 2.6 for now? I’ll get back to you again once Paul is back.

Yeah seems to be working now.

Yes, currently Draft only supports Python 2.6, particularly the version of Python included with Deadline. Support for Python 2.7 would require a new, separate Draft build.

Privacy | Site terms | Cookie preferences