I encountered the same mysterious symptom, but in a completely different
context. DLLs mis-matched. Might be of use to you...
http://curl.haxx.se/mail/curlpython-2014-05/0010.html
On 2014-05-26 9:16 PM, Mark Hammond wrote:
I see on python-list that this was solved by running the postInstall
script manually. However, I'm surprised that is necessary - build 219
has a work-around for Python 3.4 not running the post-install script,
so that should work.
I'll try and look into how this might have happened, but if you would
like to help in the meantime, could you please re-run the pywin32
installer and (a) verify it prompted you to elevate, and (b) at the
very end of the install process, verify that the installer shows you
the output of the post-install script rather than an empty box?
Thanks,
Mark
On 27/05/2014 5:16 AM, Nagy László Zsolt wrote:
Python 3.4.1 (v3.4.1:c0e311e010fc, May 18 2014, 10:45:13) [MSC v.1600 64
bit (AMD64)] on win32
pywin32-219 (64-bit) taken from here:
http://www.lfd.uci.edu/~gohlke/pythonlibs/#pywin32
Operating system: Windows 7 64bit
Path=C:\Python34\;C:\Python34\Scripts;C:\Program Files (x86)\NVIDIA
Corporation\PhysX\Common;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\Program
Files\SlikSvn\bin;C:\texlive\2013\bin\win32;c:\Python34\DLLs;c:\Python27\DLLs
If I start up Python 3.4 and do "import win32service" then I get:
ImportError: DLL load failed: The specified module could not be found
(The actual error message is in Hungarian because I have a hungarian
windows but I guess that doesn't count)
If I do the same with Python 2.7 then it succeeds.
This is a cross post from the main python-list.
Thanks,
Laszlo
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
