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 cgohlke, jkloth, methane, ned.deily, paul.moore, steve.dower, tim.golden, zach.ware
Date 2017-10-07.05:00:06
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1507352407.47.0.213398074469.issue31340@psf.upfronthosting.co.za>
In-reply-to
Content
> How about giving priority to VS 2015

That would be the fix, but it's not worth releasing an immediate 3.6.4 IMHO and by the time 3.6.4 comes about it could be more pain to change back than to leave it. That's the balance I'm thinking about for a while.

Including Ned so he's aware. If we do a snap 3.6.4 for some other reason then it's worth swapping the order, but after a few months out there I think the damage, small as it is, will have been dealt with.
History
Date User Action Args
2017-10-07 05:00:07steve.dowersetrecipients: + steve.dower, paul.moore, tim.golden, jkloth, ned.deily, methane, cgohlke, zach.ware
2017-10-07 05:00:07steve.dowersetmessageid: <1507352407.47.0.213398074469.issue31340@psf.upfronthosting.co.za>
2017-10-07 05:00:07steve.dowerlinkissue31340 messages
2017-10-07 05:00:06steve.dowercreate