VC++ versions to match python versions?
Hi All, Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...) Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?) cheers, Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
On Mon, Aug 17, 2009 at 03:22:50PM +0100, Chris Withers wrote:
Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...)
Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?)
These two I know for sure: Python 2.5: MSVC-7.1 (VC++ 2003) Python 2.6: MSVC-9.0 (VS 2008) Oleg. -- Oleg Broytmann http://phd.pp.ru/ phd@phd.pp.ru Programmers don't die, they just GOSUB without RETURN.
Hi All,
Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...) I would think so - all you really need is the compiler (which the express version definitely includes). You may need to manually add some
Chris Withers wrote: directories to the path. I haven't actually tried it, but then nor have you from the sound of it.
Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?)
Python 3.1 / 3.2 are built with VS 2008. 2.5 is built with 2003 which is difficult to download unless you have an MSDN subscription. VS 2008 can't (reliably) be used to build extensions for 2005 I believe. I'm sure someone will correct me if this information is incorrect. Michael
cheers,
Chris
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
Michael Foord wrote:
Chris Withers wrote:
Hi All,
Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...) I would think so - all you really need is the compiler (which the express version definitely includes). You may need to manually add some directories to the path.
I haven't actually tried it, but then nor have you from the sound of it.
Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?)
Python 3.1 / 3.2 are built with VS 2008. 2.5 is built with 2003 which is difficult to download unless you have an MSDN subscription. VS 2008 can't (reliably) be used to build extensions for 2005 I believe.
D'oh. For 2.5 I mean. It may be *possible* though - just as you *can* build extensions for Python 2.5 on windows with mingw (with the appropriate distutils configuration), but there are pitfalls with doing this. Michael
I'm sure someone will correct me if this information is incorrect.
Michael
cheers,
Chris
-- http://www.ironpythoninaction.com/ http://www.voidspace.org.uk/blog
Michael Foord wrote:
D'oh. For 2.5 I mean. It may be *possible* though - just as you *can* build extensions for Python 2.5 on windows with mingw (with the appropriate distutils configuration), but there are pitfalls with doing this.
Yes, in my case I'm trying to compile guppy (for heapy, which is an amazing tool) but that blows up with mingw... (But I'm also likely to want to do some python dev on windows, httplib download problems and all...) Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Chris Withers wrote:
Michael Foord wrote:
D'oh. For 2.5 I mean. It may be *possible* though - just as you *can* build extensions for Python 2.5 on windows with mingw (with the appropriate distutils configuration), but there are pitfalls with doing this.
Yes, in my case I'm trying to compile guppy (for heapy, which is an amazing tool) but that blows up with mingw...
(But I'm also likely to want to do some python dev on windows, httplib download problems and all...)
Chris
Guppy doesn't compile on Windows. Pretty much full-stop. It uses static references to DLL functions, which on Windows is not allowed. I've tried patching it to remove such things, and I finally got it to compile, only to have it go "boom!" in actual use. If you can get it to work, certainly post something so that I can cheer. John =:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqJc8EACgkQJdeBCYSNAAPFWgCghbyZ4MDcA3xich0mBOO1/VoY 5mcAnjjv1kS8Ln3dhbG6/W75zmGacWQw =x6ZX -----END PGP SIGNATURE-----
John Arbash Meinel wrote:
Guppy doesn't compile on Windows. Pretty much full-stop. It uses static references to DLL functions, which on Windows is not allowed.
This is no longer true as of the latest version of guppy...
I've tried patching it to remove such things, and I finally got it to compile, only to have it go "boom!" in actual use.
If you can get it to work, certainly post something so that I can cheer.
Are you on the guppy list? Someone posted a patch to it (which may have been you?) which has made it into the latest release. I haven't tried to get it working myself yet, but John Machin (who maintains xlrd) has with the Express compiler. I was just checking I had the right version and what version I should use if I want to try with Python 2.5. I also wanted to know what versions I should be using for python core development should I be foolhardy enough to try any of that on Windows... (he says, staring down the barrel of slow httplib downloads on Windows :'( ) Will let you know what I find... Chris -- Simplistix - Content Management, Batch Processing & Python Consulting - http://www.simplistix.co.uk
Chris Withers <chris@simplistix.co.uk> writes:
Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...)
Yes - it's currently being used on my buildbot, for example, to build Python itself. Works for 2.6 and later.
Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?)
2.5 needs VS 2003. -- David
On Mon, Aug 17, 2009 at 2:01 PM, David Bolen<db3l.net@gmail.com> wrote:
Chris Withers <chris@simplistix.co.uk> writes:
Is the Express Edition of Visual C++ 2008 suitable for compiling packages for Python 2.6 on Windows? (And Python 2.6 itself for that matter...)
Yes - it's currently being used on my buildbot, for example, to build Python itself. Works for 2.6 and later.
Ditto for 2.5, 3.1 and the trunk (which I guess becomes 3.2?)
2.5 needs VS 2003.
The 64 bits version of 2.5 is built with VS 2005, though. cheers, David
participants (7)
-
"Martin v. Löwis" -
Chris Withers -
David Bolen -
David Cournapeau -
John Arbash Meinel -
Michael Foord -
Oleg Broytmann