<br><div><span class="gmail_quote">On 11/20/07, <b class="gmail_sendername">Paul Moore</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 20/11/2007, Paul Moore <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:<br>> PPS I *will* see what the current status of msvcr8/9 support in the<br>> Mingw project is, but I'm not too hopeful - mingw is currently
<br>> undergoing a change of maintainers and progress has slowed a lot.<br><br>Apologies. I had an out of date mingw runtime. It appears that msvcr80<br>*is* supported with mingw, but that's the latest.<br><br>Whether that counts as an argument for sticking with VS 2005, I don't
<br>know. I doubt it, realistically. But it *may* constitute an argument<br>for not going to VS 2008 until it's actually released (and mingw have<br>a chance to ship a runtime with appropriate CRT support).</blockquote>
<div><br>I would not hold up a compiler decision based on the mingw project. Always use the latest MS compiler released at the time for a x.0 build of any python. Doing otherwise costs the world a fortune in lost performance (higher power consumption via lower efficiency code). mingw will undoubtedly catch up on its own.