➜

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-10.23:59:11
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1544486351.47.0.788709270274.issue35433@psf.upfronthosting.co.za>
In-reply-to
Content 
(sorry for the rapid updates)

I'm also fairly sure that none of my workers have update 3 for VS2015.  They do however all have VS2017 - but I think VS2015 still gets picked for 3.6 if both are present, right?  So that's another variable, in that my workers wouldn't have run into the update 3 issue with the older configuration that Jeremy did.  

Not sure if there's a way to have the build setup to work for both cases.
History
Date User Action Args
2018-12-10 23:59:11db3lsetrecipients: + db3l, paul.moore, vstinner, tim.golden, jkloth, jeremy.kloth, zach.ware, steve.dower, pablogsal, miss-islington
2018-12-10 23:59:11db3lsetmessageid: <1544486351.47.0.788709270274.issue35433@psf.upfronthosting.co.za>
2018-12-10 23:59:11db3llinkissue35433 messages
2018-12-10 23:59:11db3lcreate