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 brett.cannon
Recipients brett.cannon, chris.jerdonek, ezio.melotti, pitrou, r.david.murray, vstinner
Date 2013-03-27.13:18:00
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1364390280.86.0.602035832585.issue17554@psf.upfronthosting.co.za>
In-reply-to
Content
So are you saying you want both the short-form output while running but then the whole output upon completion, David? I can understand wanting the summaries still in order to sort the skipped tests vs. failures, but not outputting every test that succeeded since you can figure that out through a process of elimination w/o much issue.

I think instead it would serve us better to have a command to write the tests that were run and what happened to a file for use with the -f with successes commented out, skips commented out along with the skipped message, and then only failures left uncommented for easier re-running of the tests in the same order.
History
Date User Action Args
2013-03-27 13:18:00brett.cannonsetrecipients: + brett.cannon, pitrou, vstinner, ezio.melotti, r.david.murray, chris.jerdonek
2013-03-27 13:18:00brett.cannonsetmessageid: <1364390280.86.0.602035832585.issue17554@psf.upfronthosting.co.za>
2013-03-27 13:18:00brett.cannonlinkissue17554 messages
2013-03-27 13:18:00brett.cannoncreate