Author vstinner
Recipients docs@python, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2017-05-12.09:32:47
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1494581567.83.0.310363881682.issue30350@psf.upfronthosting.co.za>
In-reply-to
Content
Steve Dower wrote this comment on my PR https://github.com/python/cpython/pull/1544 :

"Ah, I see. This is fine then - I have very little interest in doing much work to support the old build files (as they are explicitly unsupported)."

Copy of my reply:

"I have very little interest in doing much work to support the old build files (as they are explicitly unsupported)."

Wait wait wait... I fail to follow progress on the Windows build system, so I rely on the devguide which I expect to be up to date, and the guide says:

https://docs.python.org/devguide/setup.html#windows-compiling

"Python 2.7 uses Microsoft Visual Studio 2008, which is most easily obtained through an MSDN subscription."

I have a MSDN account, but after 30 min, I failed to get my MSDN number and I don't know my subscription is still valid or not (well, I guess that, it's expired). It took me 1 hour to find an old ISO of Visual Studio 2008, and not from microsoft.com :-(

I didn't want to install VS 2008, but I just followed the devguide.

... Do you mean that VS 2010 must now be used and the devguide is just outdated?


Moreover: we do have a buildbot using VS 2008. I'm now trying to fix all buildbots, so I had to fix issues on this VS 2008 buildbot too: http://bugs.python.org/issue30313

But I guess that it's ok to have a buildbot on a system not officially fully supported.
History
Date User Action Args
2017-05-12 09:32:48vstinnersetrecipients: + vstinner, paul.moore, tim.golden, docs@python, zach.ware, steve.dower
2017-05-12 09:32:47vstinnersetmessageid: <1494581567.83.0.310363881682.issue30350@psf.upfronthosting.co.za>
2017-05-12 09:32:47vstinnerlinkissue30350 messages
2017-05-12 09:32:47vstinnercreate