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 terry.reedy
Recipients terry.reedy
Date 2016-05-31.06:46:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
In msg243635 of the renaming issue #24225, Nick suggested

"One path you may want to consider is progressively factoring out a public "idlelib.extensions" API, and treat everything else in idlelib as fair game for renaming. Folks tend to be more tolerant of disruption if the new state of affairs is also clearly better for them, not just the folks making the change."

This issue is an implementation of that idea, except that I want to reserve 'extension' for modules added by 3rd parties using the extension interface.  The new module would consist of callables that make builtin IDLE features available to non-IDLE tkinter code.

The first callable would replace the following from turtledemo.__main__

from idlelib.colorizer import ColorDelegator, color_config
from idlelib.percolator import Percolator


from idlelib.interface import colorize

At the moment, interface would have the imports and 

def colorize(text):

Future enhancements might be to accept a color scheme name and to return the Percolator instance (or a wrapper thereof), but these would not break code.  In any case, colorize would be re-written if the needed incantation changed, and turtledemo would continue to work without change.

An new public module should not be backported for the usual reasons.  New callables should also not be added except in comments.  I plan to only add features that are requested, and perhaps a very few others, rather than everything and everything possible.
Date User Action Args
2016-05-31 06:46:47terry.reedysetrecipients: + terry.reedy
2016-05-31 06:46:46terry.reedysetmessageid: <>
2016-05-31 06:46:46terry.reedylinkissue27162 messages
2016-05-31 06:46:45terry.reedycreate