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 r.david.murray
Recipients r.david.murray, roger.serwy, terry.reedy
Date 2012-07-19.11:45:37
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
All the tests should run from the standard test runner tool (currently regrtest), with the GUI tests guarded by the GUI resource, which is how it works for TK.  I always run the test suite with -uall before non-trivial commits, so I do in fact run the TK gui tests on a regular basis.  I would do the same with idle.  I hope there are at least a few other developers that run with -uall on a regular basis :)

Whether or not there is value in a separate runner is a separate question.  If there is value in having one to you and the other people working on idle, then make one.  But for those of us who touch it only occasionally, the separate runner is not likely to get used.  I wasn't even aware there was one for tkinter.

There was a push a while back suggesting that best practice would be to have all tests be in the 'test' subdirectory.  I moved email/test into test/test_email, and I prefer having it there.  On the other hand, Michael prefers having unittest/test, and has kept the unittest unit tests there.  So that part is up to you, but I encourage you to consider putting them in the test subdirectory, and if you want to do that I would help out with moving the existing tkinter tests to the 'test' dir.

And yes, either way the tests should test for the presence of idle and skip if idle is not available.
Date User Action Args
2012-07-19 11:45:39r.david.murraysetrecipients: + r.david.murray, terry.reedy, roger.serwy
2012-07-19 11:45:39r.david.murraysetmessageid: <>
2012-07-19 11:45:38r.david.murraylinkissue15392 messages
2012-07-19 11:45:37r.david.murraycreate