This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author loewis
Recipients christian.heimes, craigh, loewis
Date 2008-12-07.09:09:10
SpamBayes Score 1.83742e-06
Marked as misclassified No
Message-id <>
In-reply-to <>
> I understand the rationale behind #4120, but it seems like it only helps
> a narrow set of applications, namely "applications that link dynamically
> with the same version of MSVCR90 as Python and that bundle the MSVCR90
> DLL and that can't install the VS2008 redist". 

This is not a narrow set, though. It includes all the applications that
use py2exe and friends to create stand-alone applications. This case
absolutely must be supported.

> The 2.6.0 behavior - requiring the VS2008 redist to be installed - is
> hardly perfect (to put it mildly), but in my opinion it's more obvious
> and straightforward, and more consistent with the behavior of other
> Windows software.

Python has a long tradition of supporting "xcopy deployment". I don't
want Microsoft to dictate that we stop supporting that. I find the need
to have end-users install the CRT redist particularly unacceptable.

I don't quite understand this issue yet. python26.dll is linked with
a manifest. Isn't that good enough?
Date User Action Args
2008-12-07 09:09:14loewissetrecipients: + loewis, christian.heimes, craigh
2008-12-07 09:09:13loewislinkissue4566 messages
2008-12-07 09:09:11loewiscreate