Re: [Python-Dev] Microsoft Visual C++ Compiler for Python 2.7

2014-09-29 Thread Giampaolo Rodola' 
On Fri, Sep 26, 2014 at 8:01 PM, Steve Dower 
wrote:

> Hi all,
>
> (This is advance notice since people on this list will be interested.
> Official announcements are coming when setuptools makes their next release.)
>
> Microsoft has released a compiler package targeting Python 2.7 (i.e. VC9).
> We've produced this package to help library developers build wheels for
> Windows, but also to help users unblock themselves when they need to build
> C extensions themselves.
>
> The Microsoft Visual C++ Compiler for Python 2.7 is available from:
> http://aka.ms/vcpython27
>
> This package contains all the tools and headers required to build C
> extension modules for Python 2.7 32-bit and 64-bit (note that some
> extension modules require 3rd party dependencies such as OpenSSL or libxml2
> that are not included). Other versions of Python built with Visual C++ 2008
> are also supported.
>
> You can install the package without requiring administrative privileges
> and, with the latest version of setuptools (when it releases), use tools
> such as pip, wheel, or a setup.py file to produce binaries on Windows.
>
> Unfortunately, this package isn't necessarily going to help with building
> CPython 2.7 itself, as the build process is complicated and Visual Studio
> 2008 is practically required. However, as most people aren't building
> CPython on Windows, this isn't a huge issue. This compiler package should
> be sufficient for most extension modules.
>
> I should also point out that VC9 is no longer supported by Microsoft. This
> means there won't be any improvements or bug fixes coming, and there's no
> official support offered. Feel free to contact me directly <
> [email protected]> if there are issues with the package.
>
> Cheers,
> Steve
>
> ___
> Python-Dev mailing list
> [email protected]
> https://mail.python.org/mailman/listinfo/python-dev
> Unsubscribe:
> https://mail.python.org/mailman/options/python-dev/g.rodola%40gmail.com
>

This is awesome, thanks.
I guess Python 2.6 is not supported, isn't it?

-- 
Giampaolo - http://grodola.blogspot.com
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com

Re: [Python-Dev] Microsoft Visual C++ Compiler for Python 2.7

2014-09-29 Thread Steve Dower 
Paul Moore wrote:
> File "C:\Apps\Python27\Lib\distutils\msvc9compiler.py", line 299, in
> query_vcvarsall
> 
> raise ValueError(str(list(result.keys(
> 
> ValueError: [u'path', u'include', u'lib']
> 
> 
> Failed building wheel for blist
> Failed to build blist
> Cleaning up...
> 
> 
> PS 15:36 [00:02] C:\Work\Projects\buildwheel
> >.\ve-2.7\Scripts\pip.exe list
> pip (1.5.6)
> setuptools (6.0.1)
> wheel (0.24.0)
> 
> This looks suspiciously like http://bugs.python.org/issue7511, which is
> worrying. Is this not something I should have expected setuptools to have
> patched?

Always embarrassing to have to admit this, but there is a bug in my code... :(

distutils validates that four environment variables are set after the 
vcvarsall.bat script - PATH, INCLUDE, LIB and LIBPATH. I neglected to set 
LIBPATH for 64-bit targets (LIBPATH is used by the compiler when compiling with 
/clr, which probably no Python extension has done ever).

If you have a dirty machine like mine, then it's probably already set globally, 
which can really mess up your testing.

I'm putting up an updated installer for the compilers that will set this 
variable, so if you haven't grabbed a copy yet hold off for the next 12 hours 
or so. Otherwise, you can set your LIBPATH variable to any valid path (or maybe 
just any value - the compiler may not even look if /clr is not passed).

Sorry,
Steve

> Paul
___
Python-Dev mailing list
[email protected]
https://mail.python.org/mailman/listinfo/python-dev
Unsubscribe: 
https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com