[Python-Dev] Switch to MS VC++ 2005 ?! (original) (raw)

martin at v.loewis.de martin at v.loewis.de
Mon Feb 27 21:12:35 CET 2006

Zitat von "M.-A. Lemburg" <mal at egenix.com>:

> What I hear from the rumor mill (not perhaps a reliable source) is a > bit discouraging about the stability of VS2005 (e.g. internal > rebellion at MS in which groups which need to ship a lot of code > pushed back against any attempt to make them use VS2005, and managed > to win the internal fight and stick with VS2003), but I don't know if > any such worry applies to something as simple as the mere compilation > of C code...

Should I read this as: VC8 is unstable ?

Not sure how Alex interprets this; I think that one of the good reasons not to use VS2005 is that they managed to "break" the C library: change it from standard C in an incompatible way that they think is better for the end user. One of these changes broke Python; we now have a work-around for this breakage.

In addition to changing the library behaviour, they also produce tons of warnings about perfectly correct code.

Well, the code that VC7 generates relies on MSVCR71.DLL which appears to be part of .NET 1.1. It's hard to tell since I don't have a system around without .NET on it.

I don't believe .NET 1.1 ships msvcr71.dll. Actually, Microsoft discourages installing msvcr into system32, so that would be against their own guidelines.

Regards, Martin

More information about the Python-Dev mailing list