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
sc
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
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
Corpora
