win32com client and McMillan installer 5.3b1
francis.meyvis at sonycom.com
Fri Mar 29 12:06:02 CET 2002
I found a miserable work around.
The pythoncom16.dll is somewhere under the WINNT.
I copied this as pythoncom.dll and the thing now works.
Does someone have a nicer solution?
Kind regards, best wishes,
Francis Meyvis <francis.meyvis at sonycom.com> wrote in message
news:FVWo8.9$ta.1379 at nreader3.kpnqwest.net...
> I've a bunch of python scripts that I'd like to convert into and exe.
> This works well with the McMillan Installer except the script that
> uses the win32com client stuff to access worksheets in an excell document.
> From the traceback I see that there's an import error:
> "No module named pythoncom"
> I tried it with McMillan installer 5.3b1 on
> NT5 with python 2.2 and Mark Hammond's associated win32 extentions
> NT4 with python 1.6 and Mark Hammond's associated win32 extentions
> Both give me the same result.
> Can someone point me to what I'm doing wrong?
> I did a
> p22 Makespec.py --name=tst script.py
> p22 Build.py script.py
> I have some warnings about a delayed __import__
> According to the doc these have to be taken serious.
> But the doc does not explain in a clear way to me
> what I should do about it.
> Extend the path?, add the modules manually to the spec file?
> Kind regards, best wishes,
> francis meyvis
More information about the Python-list