<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=windows-1256">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>
<div style="font-family:Calibri,sans-serif; font-size:11pt">"For the paid versions, I'm going to assume that anyone who paid for a<br>
compiler and doesn't know where their copy is, probably can't be<br>
helped ;-)"<br>
<br>
You could link to visualstudio.com for the trial versions, and maybe to a page/post about the PSF's grants process if such a page exists.<br>
<br>
"And of course there's the awkward problem that VS 2010 Express is<br>
unsupported and therefore no longer available from *any* official<br>
location. I can't solve that, sadly"<br>
<br>
These are still at http://www.visualstudio.com/en-us/downloads/download-visual-studio-vs#DownloadFamilies_4, which is the main download page. Hopefully they don't go away before 3.5, but I have no control over that unfortunately.<br>
<br>
The link I posted for 2.7 was aka.ms/vcpython27, which is a redirect that I own and can update if necessary.<br>
<br>
Cheers,<br>
Steve<br>
<br>
Top-posted from my Windows Phone</div>
</div>
<div dir="ltr">
<hr>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">From:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:p.f.moore@gmail.com">Paul Moore</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Sent:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">ý10/ý29/ý2014 15:48</span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">To:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:ethan@stoneleaf.us">Ethan Furman</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Cc:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt"><a href="mailto:python-dev@python.org">Python Dev</a></span><br>
<span style="font-family:Calibri,sans-serif; font-size:11pt; font-weight:bold">Subject:
</span><span style="font-family:Calibri,sans-serif; font-size:11pt">Re: [Python-Dev] Status of C compilers for Python on Windows</span><br>
<br>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 29 October 2014 22:19, Ethan Furman <ethan@stoneleaf.us> wrote:<br>
>> Yeah, I wondered about that. I'll work up a patch for that. But the<br>
>> more I think about it, it really is trivial:<br>
><br>
> I am reminded of an interview question I was once asked which was prefaced<br>
> with: "Here's an easy one..."<br>
><br>
> My reply was, if you know the answer, it's easy!<br>
<br>
Yeah, I know what you mean. My take on this is that I agree it's not<br>
easy if you don't know and can't get access to the information, but if<br>
you can, there's very little to it.<br>
<br>
>> - For non-free MSVC, install the appropriate version, and everything just<br>
>> works.<br>
>> - For Python 2.7 (32 or 64 bit), install the compiler for Python 2.7<br>
>> package and everything just works as long as you're using setuptools.<br>
>> - For 32 bit Python 3.2-3.4, install Visual Studio Express and<br>
>> everything just works.<br>
>> - For 64 bit Python 3.2-3.4, install the SDK, set some environment<br>
>> variables, and everything just works.<br>
>> - For Python 3.5+, install the current Visual Studion Express and<br>
>> everything just works.<br>
><br>
><br>
> I would suggest<br>
> - where to get these packages<br>
<br>
Conceded. Working out how to point people at stuff on MSDN is a<br>
challenge, things seem to move around. Maybe Steve Dower could help<br>
here with canonical URLs for some of them (IIRC, he provided one for<br>
the VS compilers for Python 2.7 package when it was announced).<br>
<br>
For the paid versions, I'm going to assume that anyone who paid for a<br>
compiler and doesn't know where their copy is, probably can't be<br>
helped ;-)<br>
<br>
And of course there's the awkward problem that VS 2010 Express is<br>
unsupported and therefore no longer available from *any* official<br>
location. I can't solve that, sadly.<br>
<br>
> - where to get any dependencies<br>
<br>
There are none. I could state that explicitly, I guess.<br>
<br>
> - any options to [not] specify during install<br>
<br>
I'll have to go through the installs again just to be sure, but I'm<br>
pretty certain "Select the default for everything" is correct.<br>
<br>
> - what environment variables to what value<br>
<br>
None, except for the SDK which I did say I needed to test out and<br>
cover in more detail.<br>
<br>
> - where one should be at when one starts the compile process<br>
<br>
I don't understand this. It's just "pip wheel foo" to build a wheel<br>
for foo (which will be downloaded), or "pip wheel ." or "python<br>
setup.py bdist_wheel" as you prefer for a local package. That's<br>
standard distutils/setuptools/pip extension building. I don't propose<br>
to cover that, just how to *set up* the environment.<br>
<br>
With the sole exception of the SDK case, once installed, everything<br>
just works everywhere, nothing to set up, no special environment to<br>
configure. Start up a new cmd or powershell console (or use the one<br>
you're already in) and go. Maybe Unix users expect more complexity<br>
because it's not that simple on Unix? But I thought it was - install<br>
the appropriate OS packages and that's it?<br>
<br>
> and, of course, a gotchas section for uncommon but frustrating things that<br>
> might go wrong.<br>
<br>
Hmm, I see your point here, but I'm not sure what I might include. You<br>
*can* get in a mess [1] but generally I don't as I'm an experienced<br>
Windows user. I also don't want to offer to debug and fix everyone's<br>
problems in getting things set up, so offering to collect and document<br>
"common issues" that I've seen is impractical. Maybe a section<br>
entitled "Common Issues and Their Solutions", with some placeholder<br>
text saying "If you have any issues installing any of the compiler<br>
packages mentioned, please document what went wrong and how to fix it,<br>
and submit a PR!" would do?<br>
<br>
> And thanks for doing this!<br>
<br>
No problem!<br>
<br>
Paul<br>
<br>
[1] I once spent a *long* time fighting failed installs of the Windows<br>
SDK. Turns out it was because I was trying to install a 32-bit SDK on<br>
a 64-bit machine (doh!), and the installer really doesn't like that<br>
:-( About all I could say to document that is "Read the instructions<br>
properly" and "I'm sorry that the MS installers fail really badly when<br>
faced with relatively obvious idiot-user errors, but I can't do<br>
anything about it :-("<br>
_______________________________________________<br>
Python-Dev mailing list<br>
Python-Dev@python.org<br>
<a href="https://mail.python.org/mailman/listinfo/python-dev">https://mail.python.org/mailman/listinfo/python-dev</a><br>
Unsubscribe: <a href="https://mail.python.org/mailman/options/python-dev/steve.dower%40microsoft.com">
https://mail.python.org/mailman/options/python-dev/steve.dower%40microsoft.com</a><br>
</div>
</span></font>
</body>
</html>