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 michael.foord
Recipients BreamoreBoy, eric.araujo, ezio.melotti, michael.foord, piotr.dobrogost, pprokop, rhettinger
Date 2012-03-01.11:11:34
SpamBayes Score 1.287459e-09
Marked as misclassified No
Message-id <1330600295.42.0.407786400029.issue4080@psf.upfronthosting.co.za>
In-reply-to
Content
Yes, it would definitely be useful (as would a count of how far through the test run we are [27/129] style). Getting to completing (even for testing) the "extensible" unittest is something I will still do (and nose2 is being built off the prototype work I did), but isn't going to happen immediately - so it's not a good reason to hold up these improvements.

I'll be sprinting at PyCon and look at this issue then.

I'm keen to avoid proliferating command line parameters to the unittest test runner. Ezio - why would you want to disable this feature?
History
Date User Action Args
2012-03-01 11:11:35michael.foordsetrecipients: + michael.foord, rhettinger, ezio.melotti, eric.araujo, pprokop, BreamoreBoy, piotr.dobrogost
2012-03-01 11:11:35michael.foordsetmessageid: <1330600295.42.0.407786400029.issue4080@psf.upfronthosting.co.za>
2012-03-01 11:11:34michael.foordlinkissue4080 messages
2012-03-01 11:11:34michael.foordcreate