It appears that pywintypes34.dll won't be loaded automatically when it's copied
beside
python.exe, but will load when copied to system32. May be due to python using
the flag
LOAD_WITH_ALTERED_SEARCH_PATH when loading pyd's, but it will take
some more study of the MSDN docs for LoadLibraryEx.
I think this is related to the issue where the post-install script (which
copies pywintypes to
one or the other) sometimes fails. Usually you can just rerun the postinstall,
however if
not rerun with administrative privs it copies pywintypes to the root of the
python install,
and it can't be loaded when you first import another module that links to it.
Roger
"Vernon D. Cole" <vernondc...@gmail.com> wrote in message
news:cah-zgafxzvxxstryxtylbyt3daswsj9xzh8nk4pe_mr55ls...@mail.gmail.com...
> So why is _mine_ broken, too? What exactly did you clean up?
>
>
>
> On Mon, Mar 24, 2014 at 10:38 AM, Thomas Heller <thel...@ctypes.org> wrote:
>
>> Am 21.03.2014 21:22, schrieb Thomas Heller:
>>
>> [this has also been sent to the python-dev mailing list]
>>>
>>> With python 3.4 and pywin32 version 218 it is only possible
>>> to import win32com or win32api when pywintypes has been imported before.
>>>
>>
>> False alarm: after cleaning everything up and installing again this
>> works now. Sorry for the noise.
>>
>>
>> Thomas
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
python-win32 mailing list
python-win32@python.org
https://mail.python.org/mailman/listinfo/python-win32
