Author ncoghlan
Recipients gvanrossum, markroseman, ncoghlan, ned.deily, serhiy.storchaka, terry.reedy
Date 2016-05-12.06:30:04
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1463034604.15.0.678005049627.issue26993@psf.upfronthosting.co.za>
In-reply-to
Content
+1 for Ned's point that PEP 434 grants the IDLE developers *permission* to backport IDLE enhancements to maintenance releases, but doesn't *oblige* them to provide such backports.

For Python 3.6, another point to keep in mind is that if anyone particularly wants to keep the old idlelib API alive, they can either fork the existing code as a PyPI project, or create a compatibility shim that runs atop the new ttk-based API.
History
Date User Action Args
2016-05-12 06:30:04ncoghlansetrecipients: + ncoghlan, gvanrossum, terry.reedy, ned.deily, markroseman, serhiy.storchaka
2016-05-12 06:30:04ncoghlansetmessageid: <1463034604.15.0.678005049627.issue26993@psf.upfronthosting.co.za>
2016-05-12 06:30:04ncoghlanlinkissue26993 messages
2016-05-12 06:30:04ncoghlancreate