This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author db3l
Recipients db3l, jeremy.kloth, jkloth, miss-islington, pablogsal, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-11.03:06:34
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544497595.23.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content
Oh, it's not the installation itself, I'm just wondering if allowing a newer version is ok too?

Of course, it doesn't preclude expanding the build script in the future, so I've installed 15063 to both Win8/10 workers.

I don't currently have access to restart builds through the buildbot web interface any more, but if someone who does wants to rerun the last 3.6 build on each builder we can make sure this resolves the issue on those workers.  

I've done a quick manual build that compiles with the exception of not finding midl.exe for pyshellext, but that seems separate (every SDK has the binary) so I'm assuming it's environmental outside of the regular build environment.
History
Date User Action Args
2018-12-11 03:06:35db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, pablogsal, miss-islington
2018-12-11 03:06:35db3lsetmessageid: <1544497595.23.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-11 03:06:35db3llinkissue35433 messages
2018-12-11 03:06:34db3lcreate