Bob Kline wrote:
>  Trent Mick wrote:
> > Note that ActivePython 2.5 is built with VC7.1 so it depends on 
> > msvcr71.dll rather than msvcrt.dll.
>  
>  Thanks, Trent.  We had found the FAQ about upgrading msvcrt.dll for 
>  ActiveState Perl to fix the same problem, but didn't find any comparable 
>  documentation for the bug in ActiveState Python, so we just followed the 
>  link to the Microsoft KB article (and download) from the Perl article.
>  
>  Are there problems with the compiler from VS2005 that made you decide to 
>  stick with the one from VS2003?  Or is that just the same inertia that 
>  has our own projects on the same compiler as you (which turns out to be 
>  convenient for us)?  Be good to know of any sinkholes hiding in the 
>  newer tool set before we upgrade (if we actually do).

To stay binary compatible with the Python distro from python.org we follow 
their lead. However, yes, whether to switch compilers (*again) to VC8 (aka 
VS2005) was discussed on the core Python developer list and rejected -- at 
least for now -- the main reasoning seems to be that there wasn't yet a 
convincing enough reason to switch. VC7.1 works fine and 3rd-party extension 
developers trying to provide builds for multiple versions of Python would just 
be inconvenienced having to have a bunch of compiler versions kicking around.

http://aspn.activestate.com/ASPN/Mail/Message/python-dev/3040634


(*) Again, because (Active)Python 2.3 and before were built with VC6. 
(Active)Python 2.4 with VC7.1. Switching to VC8 for 2.5 would have been the 
third compiler change in as many releases.


Cheers,
Trent

-- 
Trent Mick
trentm at activestate.com
_______________________________________________
ActivePython mailing list
ActivePython@[...].com
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
Other options: http://listserv.ActiveState.com/mailman/listinfo/ActivePython