Message178156
| Author | skrah |
|---|---|
| Recipients | brett.cannon, eric.araujo, ezio.melotti, serhiy.storchaka, skrah, zach.ware |
| Date | 2012-12-25.17:02:18 |
| SpamBayes Score | -1.0 |
| Marked as misclassified | Yes |
| Message-id | <20121225170220.GA13264@sleipnir.bytereef.org> |
| In-reply-to | <1356449797.2.0.638606452828.issue16748@psf.upfronthosting.co.za> |
| Content | |
|---|---|
I finally understood the issue. So this does not work:
./python -m unittest discover Lib/test/ 'test_dec*.py'
Neither does this:
./python -m unittest discover Lib/test/ 'test_multipro*.py'
And this fails, too (still hanging):
./python -m unittest discover Lib/test/ 'test_thread*.py'
I'm not sure why tests in the Python test suite should be discoverable.
If I read this ...
http://www.voidspace.org.uk/python/weblog/arch_d7_2009_05_30.shtml
..., the feature is for projects that don't have a test collection machinery. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012-12-25 17:02:18 | skrah | set | recipients: + skrah, brett.cannon, ezio.melotti, eric.araujo, zach.ware, serhiy.storchaka |
| 2012-12-25 17:02:18 | skrah | link | issue16748 messages |
| 2012-12-25 17:02:18 | skrah | create | |