[Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now (original) (raw)
Michael Foord fuzzyman at voidspace.org.uk
Tue Jan 20 14:13:16 CET 2009
- Previous message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Next message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tim Lesher wrote:
On Tue, Jan 20, 2009 at 08:02, Luke Kenneth Casson Leighton <luke.leighton at googlemail.com> wrote:
of course - if python for win32 ENTIRELY DROPPED msvc as a development platform, and went for an entirely free software development toolchain, then this problem goes away.
That's a non-starter for anyone who incorporates Python in an existing MSVC-based development environment. When in Rome... There would also be a significant performance cost. The PGO (Profile Guided Optimisation) compilation of Visual Studio is impressive.
Michael
-- http://www.ironpythoninaction.com/
- Previous message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Next message: [Python-Dev] compiling python2.5 (msys+mingw+wine) - giving up using msvcr80 assemblies for now
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]