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 ned.deily
Recipients berker.peksag, jmadden, methane, minrk, ned.deily, serhiy.storchaka, vstinner, wenzel, xiang.zhang
Date 2016-12-15.08:41:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
It appears this issue has stalled again.  Is the most recent patch fix28147-py36-2.patch) ready for review?  If so, can someone please review it?  Then it needs to be pushed to the 3.6 branch for 3.6.1 and exposed to the buildbots.  Only then could we consider cherrypicking for 3.6.0 and a change of the magnitude in the patch would require at least another preview release and delay 3.6.0 final. 3.6.0 is scheduled to be released tomorrow. I am very reluctant to delay now for an issue that has been open now for 3 months throughout the beta phase of the release cycle.  If enough people feel we should delay 3.6.0 to address this, we can.  But without a fix reviewed and committed and without more feedback from other core developers, 3.6.0 is going out without it.  @inada.naoki ? @haypo ? @serhiy.storchaka ?  Others?
Date User Action Args
2016-12-15 08:41:37ned.deilysetrecipients: + ned.deily, vstinner, methane, berker.peksag, serhiy.storchaka, minrk, jmadden, xiang.zhang, wenzel
2016-12-15 08:41:37ned.deilysetmessageid: <>
2016-12-15 08:41:37ned.deilylinkissue28147 messages
2016-12-15 08:41:36ned.deilycreate