acx01bc added the comment:
@steve.dower : the vc_redist packages doesn't list the files it installs, I'm
not sure of the names of the files, but who cares, please look at my screenshot
of dependency walker, it shows how different versions of Python win32 releases
that I dow
Changes by acx01bc :
--
status: open -> closed
___
Python tracker
<http://bugs.python.org/issue25223>
___
___
Python-bugs-list mailing list
Unsubscrib
acx01bc added the comment:
On Vista32bits, the VC++2015 redist package does install msvcr140.dll but none
of the api-ms-win-crt-***-l1-1-0.dll, thus (that's why I opened this discussion
at first) it is impossible to make many of the Python releases working, at
least on Vista 32bits.
Ther
acx01bc added the comment:
With dependency walker I see that :
- in 3.4.3, Python34.exe and also Python.34.dll have been dynamically linked
with msvcr100.dll (platform target : v100 in Visual C++ project properties),
- while in 3.5.0 (the one you download on python.org main page) Python35.exe
New submission from acx01bc:
I think you should build Python.exe with the option to be statically linked to
the VC++-runtime. This way, the executable is a little bigger, but you ensure
nobody will have troubles with some VC-runtime different Dll versions.
DETAILS : (I posted it also there
Changes by acx01bc :
--
title: Statically or dynamically linked to the VC++runtime ? or how Python
install fails o Vista despite the VC redist packages -
api-ms-win-crt-runtime-l1-1-0.dll -> Statically or dynamically linked to the
VC++runtime ? or how Python install fails on Vi
