Skip to main content

Python on Windows and the PATH

Took me a few hours to track down a problem with importing win32com and getting "ImportError: DLL load failed: The specified module could not be found" which wasn't very clear. I doesn't even say what DLL it can't find!

Long story short, it boils down to python not being able to find the pywintypes25.dll, which is located in C:\Python24, but which is not in the PATH. Seems like having C:\Python25 added to PATH or some other solution would be a good idea. The problem wasn't even with the pywin32 package, which is what I expected and where I kept looking, but in the configuration and runtime environment of the python interpreter.

Comments

Anonymous said…
FileMonitor helps you
http://www.microsoft.com/technet/sysinternals/utilities/filemon.mspx
Anonymous said…
+1, had a similar problem and this helped me find the missing dll that was being searched for.
Cheers!
Ganesh Shamnur said…
It is not about the path alone:
If the current DLL being loaded refers to an additional DLL, the referred DLL needs to be present in the PYTHONPATH.
e.g:
a.dll is being loaded in python.
a.dll was created refering to b.dll.
So, make sure that both a.dll and b.dll are in the PYTHONPATH for proper loading.
Anonymous said…
Thank you for all your comments!

Had a similar problem, a dll (in PYTHONPATH) was loading an additional dll - it did not show it's name. I used Process Monitor (the new FileMonitor) to find out what that missing file was.
Ramprasad N said…
When I get the error "ImportError: DLL load failed: The specified module could not be found." in python, how can I know which dll it is searching for?
I dont know whether the reply will automatically reach my mail inbox. so please also mail me the reply to ramprasad85 at gmail.com

Thanks you
Anonymous said…
I'm not sure how old these comments are, but I'll add a comment since this is the first response in google for "python dll load failed."

I was able to fix this by importing pywintypes before win32api in the file that was producing the error. Give this a try, it fixed the problem for me...I guess we'll see if it causes a problem somewhere else...
Christopher said…
the pywintypes worked for me as well. Python3.2 here.

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

The Range of Content on Planet Python

I've gotten a number of requests lately to contribute only Python related material to the Planet Python feeds and to be honest these requests have both surprised and insulted me, but they've continued. I am pretty sure they've come from a very small number of people, but they have become consistent. This is probably because of my current habit of writing about NaNoWriMo every day and those who aren't interested not looking forward to having the rest of the month reading about my novel. Planet Python will be getting a feed of only relevant posts in the future, but I'm going to be honest: I am kind of upset about it. I don't care if anyone thinks it is unreasonable of me to be upset about it, because the truth is Planet Python means something to me. It was probably the first thing I did that I considered "being part of the community" when I submitted my meager RSS feed to be added some seven years ago. My blog and my name on the list of authors at Plan

Javascript Module Loaders Considered Harmful

Introduction I’m coming to an opinion of Javascript module loaders that is profoundly negative and I’d like to express why I think they are, generally, a bad idea. However, I do think they have a place, which I’ll get to at the end. Now, I understand I might be in the minority here. Between the competing specifications of CommonJS and AMD modules, loader systems like RequireJS or the (honestly really awesome) Google Module Server, and the huge cultural influence of Node on the Javascript world, you’d be hard pressed to argue against Javascript modules these days. Scripts are old hat, too stupid, too inflexible. Everyone knows that and no one would make an argument in their favor, right? I’m going to step out on a limb and say “Javascript Module Loaders Considered Harmful” and I know the baggage involved with declaring something “Considered Harmful”. I mean every ounce of context that phrase carries with it, and I hope I can persuade you. Harm #1: Confused Debuggers