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 ezio.melotti
Recipients JayKrish, Todd.Rovito, Tomoki.Imai, ezio.melotti, francismb, ncoghlan, ned.deily, r.david.murray, roger.serwy, terry.reedy, tshepang
Date 2013-04-23.07:30:21
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
If things are fixed/added/improved on 3.x, there should be tests for them, and if they are backported on 2.7, tests should be backported as well.
If mock makes testing easier, I think it would be acceptable to use it and then have IDLE devs install a 2.7 mock and use it to run all the tests.  The tests on 2.7 could use skip decorators to be skipped if mock is missing, without having to keep these tests separate from the rest.  If necessary a script to install mock on 2.7 could be provided, and possibly used by the buildbots too.

This means that the initial framework should be backported, otherwise it won't be possible to backport any of tests that are going to use it.
FWIW the attached patch should use unittest.main() instead of test_main+run_unittest.
Date User Action Args
2013-04-23 07:30:22ezio.melottisetrecipients: + ezio.melotti, terry.reedy, ncoghlan, ned.deily, roger.serwy, r.david.murray, Todd.Rovito, tshepang, francismb, JayKrish, Tomoki.Imai
2013-04-23 07:30:22ezio.melottisetmessageid: <>
2013-04-23 07:30:22ezio.melottilinkissue15392 messages
2013-04-23 07:30:21ezio.melotticreate