➜

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 jkloth
Recipients jeremy.kloth, jkloth, miss-islington, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2018-12-10.05:47:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544420862.91.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content 
I've added a PR for 3.6 using a different methodology for finding the available SDK.

Without some change, my buildbot will continue to stay in the red (for 3.6).  It does not the the highest SDK currently (previously?) listed the hard-coded list.  It has the latest (17763), the latest for VS2015 (14393) and the baseline (10586).  I would like to see a working build for VS2015 on 3.6.  Once 3.6 is wrapped, I'll update the buildbot to VS2017 as that is what is listed in the README for building 3.7+, whereas 3.6 lists VS2015.
History
Date User Action Args
2018-12-10 05:47:42jklothsetrecipients: + jkloth, paul.moore, vstinner, tim.golden, jeremy.kloth, zach.ware, steve.dower, miss-islington
2018-12-10 05:47:42jklothsetmessageid: <1544420862.91.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-10 05:47:42jklothlinkissue35433 messages
2018-12-10 05:47:42jklothcreate