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 steve.dower
Recipients db3l, eric.snow, eryksun, jkloth, lukasz.langa, mattip, ncoghlan, pablogsal, paul.moore, ralf.gommers, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-03-30.23:30:24
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1553988624.95.0.631337134165.issue36085@roundup.psfhosted.org>
In-reply-to
Content
I attached a build of the updated installer to PR 12636 (it's too big to attach here) in case anyone can help me test. It should block right at the start if you don't have the update, or else it'll go to the usual screen.

The message just says "install SP1 and all updates" as it always has, though the log file specifically refers to the KB. I doubt enough people are going to hit this for it to be a huge problem.

Also, I think Eryk was right that Windows 8 apparently does require the additional flag. It shouldn't affect what the test is testing, so I put it in for all versions. Just waiting on the custom buildbot to start to verify that the flag is all that's necessary and not the other changes I tried.
History
Date User Action Args
2019-03-30 23:30:24steve.dowersetrecipients: + steve.dower, paul.moore, db3l, ncoghlan, vstinner, tim.golden, jkloth, lukasz.langa, eric.snow, zach.ware, mattip, eryksun, ralf.gommers, pablogsal
2019-03-30 23:30:24steve.dowersetmessageid: <1553988624.95.0.631337134165.issue36085@roundup.psfhosted.org>
2019-03-30 23:30:24steve.dowerlinkissue36085 messages
2019-03-30 23:30:24steve.dowercreate