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
Am 24.03.2014 21:25, schrieb Vernon D. Cole:
So why is _mine_ broken, too?
No idea.
What exactly did you clean up?
I ran the bdist_wininst uninstaller, then ran 'pip uninstall pywin32'
and installed the bdist_wininst installer again then it worked.
Previously I probably had a mess of inst
So why is _mine_ broken, too? What exactly did you clean up?
On Mon, Mar 24, 2014 at 10:38 AM, Thomas Heller 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
>>
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 aga
Am 21.03.2014 22:18, schrieb Vernon D. Cole:
Mark & Crew:
We have a serious problem with the Python 3.4 64-bit release. This
is not just a weird adodbapi bug. The IDE will not run, either.
I have created http://bugs.python.org/issue21050 in the python bug tracker.
Thomas
--
Vernon
Inlin
[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.
I have no idea if this is a bug in pywin32 or in Python 3.4.
Does anyone know more?
Thanks,
Thomas
_
