[Idle-dev] A plan to fix IDLE while waiting for PEP434

[Todd V Rovito]

On Mar 28, 2013, at 11:51 PM, Roger Serwy <roger.serwy at gmail.com> wrote:

> Hi Everyone,
> 
> There are 107 open issues against IDLE presently in the bug tracker. Here is a list of 31 issues that deal with actual bugs in IDLE. These are not enhancements, new features, user-interface annoyances, or anything requiring a change to how the user interacts with IDLE (with the arguable exceptions of 14105 and 14146). Let's fix these issues while we wait on PEP434.
> 
> We still need a unit test framework for IDLE as listed in 15392. Full unit testing would require a significant refactoring of parts of IDLE. I am willing to accept extensive manual testing for an issue as sufficient reason to apply a patch, but if a very simple test can be written then let's write it with the hope of later incorporating it into a framework.
> 
Count me in, thanks for providing a list now I know where to start.  On the unit tests it is difficult to know what to write without an existing framework but I will give it a try.