pyWin32-py3.5 uses a different vc runtime than python 3.5

Hi I just found an issue with pyWin32 failing to install on a system that doesn't have the vc2010 runtime loaded.
The pyd dll files still depend of the vc2010 runtime but python 35 now uses the vc2015 runtime (non xp).
(only tested the 64 bit build but I also see that the 32 bit pyd files still depend on MSVCR100.dll)

*I think this could cause issues (like heap corruption) if the runtimes are different.

Note though that the vc2015 runtime that python 35 uses is isolated in the python root folder - and may be a different version than the official MS install -- which is actually the case now as vc2015 update 1 has been relaeased.

This is the issue behind bug #706
https://sourceforge.net/p/pywin32/bugs/706/

Reported by: bmiller_qw

Original Ticket: pywin32/bugs/708

Try the binaries http://www.lfd.uci.edu/~gohlke/pythonlibs/#pywin32, which are built with the correct compilers.

Original comment by: cjgohlke

Thanks, that worked great!
I've used your fantastic site in the past - I didn't even think of checking for pywin32 builds there.
I can't imagine the pain & suffering it takes to build all those libs...

Original comment by: bmiller_qw

This issue should also be fixed in the official pywin32-220 builds at http://sourceforge.net/projects/pywin32/files/pywin32/Build%20220/

Original comment by: cjgohlke

[Avasam]

.exe/binary installers are now deprecated #1939 and wheels for all bitness are available on PyPI
This issue should also be fixed in pywin32>=220