Nick Coghlan added the comment: +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. ---------- _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26993> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
