Message190166
Before committing, I experimented with disabling test/test_idle. The simple and safe method is to comment out the 'load_tests' line. With no tests discovered, all pass ;-). Without verbosity, there is no indication that there were none. A little harder, and needing to be tested for typos before committing, is to add this line before that line:
import unittest; raise unittest.SkipTest('skip for buildbots')
Regrtest (py -m test test_idle) registers the unexpected skip. Unittest (py -m test.test_idle) exits with a traceback. This is recorded in an updated README, which also incorporates Todd's suggestion. I also touched up test/test_idle.py.
If buildbots do not break, I will work on 2.7. |
|
Date |
User |
Action |
Args |
2013-05-28 01:35:16 | terry.reedy | set | recipients:
+ terry.reedy, ncoghlan, ned.deily, ezio.melotti, roger.serwy, r.david.murray, Todd.Rovito, tshepang, python-dev, francismb, Guilherme.Simões, JayKrish, Tomoki.Imai, alex.rodas |
2013-05-28 01:35:16 | terry.reedy | set | messageid: <1369704916.38.0.612816703663.issue15392@psf.upfronthosting.co.za> |
2013-05-28 01:35:16 | terry.reedy | link | issue15392 messages |
2013-05-28 01:35:15 | terry.reedy | create | |
|