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 ncoghlan
Recipients Al.Sweigart, kbk, ncoghlan, roger.serwy, serhiy.storchaka, terry.reedy
Date 2015-05-19.23:35:58
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1432078558.38.0.554612829086.issue24225@psf.upfronthosting.co.za>
In-reply-to
Content
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.

In terms of supporting legacy module names without retaining all that complexity in the main source code, I'd suggest looking into the way the "six.moves" module works.
History
Date User Action Args
2015-05-19 23:35:58ncoghlansetrecipients: + ncoghlan, terry.reedy, kbk, roger.serwy, Al.Sweigart, serhiy.storchaka
2015-05-19 23:35:58ncoghlansetmessageid: <1432078558.38.0.554612829086.issue24225@psf.upfronthosting.co.za>
2015-05-19 23:35:58ncoghlanlinkissue24225 messages
2015-05-19 23:35:58ncoghlancreate