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 loewis, serhiy.storchaka, steve.dower, tim.golden, zach.ware
Date 2016-05-02.06:09:12
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
As I recall, the tool is ready to go. The problem is the argument over what to do with all the APIs that currently are incorrect. Zach had a list at PyCon last year, and the consensus seemed to be that "someone" should figure out whether each API should be stable or not. Since Zach understandably doesn't want to be that someone, there's really no way to reliably tool this process when there are a number of existing violations.

(FWIW, I believe we should just add them to the stable list, as that's the only way to guarantee source compatibility. They've already shipped in 3.5 and people can use them on non-Windows OSs.)
Date User Action Args
2016-05-02 06:09:12steve.dowersetrecipients: + steve.dower, loewis, tim.golden, zach.ware, serhiy.storchaka
2016-05-02 06:09:12steve.dowersetmessageid: <>
2016-05-02 06:09:12steve.dowerlinkissue23903 messages
2016-05-02 06:09:12steve.dowercreate