Hi!
When you had installed Python, had you choose "Add to path" (at end of
list of install's options)?
(sorry for my bad english)
@-salutations
--
install's
Le 27/07/2017 à 01:31, Greg Ewing a écrit :
I recently tried to install a COM server written in Python and
ran into a small problem. The procedure I used was this:
1. Install Python 3 using the standard Windows installer, as
Administrator, for All Users, adding Python to the path.
2. pip install pypiwin32
3. Run my script for registering the COM server, which
calls win32com.server.register.UseCommandLine.
This didn't work, and the reason turned out to be that the
InprocServer32 registry was just the filename of the dll,
rather than a full pathname. When I changed it to an
absolute pathname, the server worked fine.
The standard win32com code for server registration seems to
be assuming that pythoncom.dll and winctypes.dll have been
installed in C:\Windows\System32. However, pip doesn't
put them there, and I get the impression that installing
all DLLs there is no longer considered best practice.
I found an old sourceforge bug report about this:
https://sourceforge.net/p/pywin32/bugs/393/
which suggests a one-line change to win32com\server\register.py
to address this problem, but it was closed with works-for-me.
Am I right that using a relative pathname for InprocServer32 is
no longer the right thing to do? Should I reopen this issue?
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
