Message77217
| Author |
loewis |
| Recipients |
christian.heimes, craigh, loewis |
| Date |
2008年12月07日.09:09:10 |
| SpamBayes Score |
1.8374225e-06 |
| Marked as misclassified |
No |
| Message-id |
<493B92B4.5040104@v.loewis.de> |
| In-reply-to |
<1228620733.99.0.134856979495.issue4566@psf.upfronthosting.co.za> |
| Content |
> 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? |
|