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 r.david.murray
Recipients Edward.K..Ream, SilentGhost, anshul6, eryksun, paul.moore, r.david.murray, random832, steve.dower, stutzbach, tim.golden, zach.ware
Date 2016-12-03.14:50:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1480776644.53.0.537266497357.issue25778@psf.upfronthosting.co.za>
In-reply-to
Content
Looks like it fell off everyone's radar.    It is now also too late in the 3.6 release cycle: it isn't "release critical" in the sense of being a breaking regression from 3.5, so it is not likely to get in.

Keep in mind that this is a distributed, mostly volunteer community.  Clearly no one else thought it was a release blocker, but you have presented a case for making it so.  I haven't evaluated that case; I'm leaving that to the windows devs.  Having your input a few weeks ago would have made it more likely to get in to 3.6, regardless of whether or not anyone else thought it was a release blocker.

And please check back after the 3.6 release, and advocate for getting it in to the next release of both 3.5 and 3.6.
History
Date User Action Args
2016-12-03 14:50:44r.david.murraysetrecipients: + r.david.murray, paul.moore, tim.golden, stutzbach, SilentGhost, zach.ware, eryksun, steve.dower, Edward.K..Ream, random832, anshul6
2016-12-03 14:50:44r.david.murraysetmessageid: <1480776644.53.0.537266497357.issue25778@psf.upfronthosting.co.za>
2016-12-03 14:50:44r.david.murraylinkissue25778 messages
2016-12-03 14:50:44r.david.murraycreate