If you expand the Details section, it says the version is 7.1.
On Thu, Jan 15, 2015 at 3:58 PM, Victor Stinner
wrote:
> 2015-01-15 22:39 GMT+01:00 Ryan Gonzalez :
> > http://www.microsoft.com/en-us/download/details.aspx?id=8279
>
> "Microsoft Windows SDK for Windows 7 and .NET Framework 4"
>
> A
Oh by the way, the tool that I wrote to build wheel packages on Windows is here:
https://code.google.com/p/tulip/source/browse/release.py
It was too annoying to have to open 6 times the Windows SDK shell, and
type each time between 2 and 4 commands.
release.py help:
--
Usage: release.py [opti
Victor Stinner wrote:
> 2015-01-15 22:39 GMT+01:00 Ryan Gonzalez :
> > http://www.microsoft.com/en-us/download/details.aspx?id=8279
>
> "Microsoft Windows SDK for Windows 7 and .NET Framework 4"
>
> Are you sure that it is SDK 7.1, and not 7.0?
The naming is horrible, and the bugs between VS and
On 15 January 2015 at 22:26, Zachary Ware wrote:
> Extension building in general is still a mess on Windows, I hope the
> links above are enough to get you going again!
For building extensions, I have a powershell script that, starting
with a clean machine, downloads and installs everything neede
On Thu, Jan 15, 2015 at 3:30 PM, Victor Stinner
wrote:
> Hi,
>
> I installed the SP1 for Visual Studio 2010, and it looks like that it
> broke my Windows SDK 7.1 (setenv was missing, cl.exe was also
> missing). I uninstalled the SDK 7.1, and then I saw that a patch is
> required to use Windows SDK
2015-01-15 22:39 GMT+01:00 Ryan Gonzalez :
> http://www.microsoft.com/en-us/download/details.aspx?id=8279
"Microsoft Windows SDK for Windows 7 and .NET Framework 4"
Are you sure that it is SDK 7.1, and not 7.0?
--
The SDK 7.0 works for Python 2.7 which is compiled with Visual Studio 2008.
I us
On Thu, Jan 15, 2015 at 3:30 PM, Victor Stinner
wrote:
> Hi,
>
> I installed the SP1 for Visual Studio 2010, and it looks like that it
> broke my Windows SDK 7.1 (setenv was missing, cl.exe was also
> missing). I uninstalled the SDK 7.1, and then I saw that a patch is
> required to use Windows SD
Hi,
I installed the SP1 for Visual Studio 2010, and it looks like that it
broke my Windows SDK 7.1 (setenv was missing, cl.exe was also
missing). I uninstalled the SDK 7.1, and then I saw that a patch is
required to use Windows SDK 7.1 with Visual Studio 2010 SP1. Ah. Too
late.
I don't understand
On Wed Jan 14 2015 at 4:58:20 PM Demian Brecht
wrote:
> On 2015-01-14 1:19 PM, Brett Cannon wrote:
> > But as Guido pointed out, we _like_ it being difficult to do because we
> > don't want this kind of substitution happening as code ends up depending
> on
> > bugs and quirks that you may fix.
>
