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 jeremy.kloth
Recipients db3l, jeremy.kloth, jkloth, miss-islington, pablogsal, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-11.03:18:13
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAGvrs3+oNTu98Pu=+DiRF3jSKvQE48xdJZw_QiukyCU7ryGLjQ@mail.gmail.com>
In-reply-to <1544497595.23.0.788709270274.issue35433@psf.upfronthosting.co.za>
Content
> Oh, it's not the installation itself, I'm just wondering if allowing a newer version is ok too?

The original PR (included in 3.7, 3.x) uses the latest discovered SDK,
but Steve stated that that logic broke the Pipelines build, so I
reworked to PR to just check for the versions already hard-coded.

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

For 3.6, this is the last hurrah.  It goes into security mode after
tonight.  Although, it does seem that we might need to add a check for
the SDK ourselves instead of relying on MSBuild to do it (it may be a
full Visual Studio only thing, not Build Tools).

> I don't currently have access to restart builds through the buildbot web interface any more

If anyone with the power to do so is watching, this is something that
I miss now, too.  It seems that the buildbot owners are not given the
proper permissions for this task.
History
Date User Action Args
2018-12-11 03:18:13jeremy.klothsetrecipients: + jeremy.kloth, paul.moore, db3l, vstinner, tim.golden, jkloth, zach.ware, steve.dower, pablogsal, miss-islington
2018-12-11 03:18:13jeremy.klothlinkissue35433 messages
2018-12-11 03:18:13jeremy.klothcreate