The suggestions so far are good. To reduce the chances that they are forgotten, it would be better to submit them as either bug fix or enhancement requests to the Python issue tracker (http://bugs.python.org/).
One area not mentioned but of critical importance is the lack in the standard library of a test suite for IDLE. Right now it is very difficult to know when things are broken or breaking because of the lack of tests. Making such a test suite presents some "interesting" challenges, though. The current python test suite does very little automated GUI interface testing so some new cross-platform infrastructure to do so would need to be added, preferably in a way that can be added to the source code tree without creating any licensing issues (i.e. not GPL). Another challenge is to do so in a way that ideally covers all of the primary IDLE execution environments: Windows, native Mac OS X, and Unix/X11. If you have ideas or experience in this area, your contributions would be especially welcome. -- Ned Deily, n...@acm.org _______________________________________________ IDLE-dev mailing list IDLE-dev@python.org http://mail.python.org/mailman/listinfo/idle-dev
