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 terry.reedy
Recipients ezio.melotti, terry.reedy, zach.ware
Date 2014-06-13.20:07:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
You might add a brief description of why this is good idea, or link to such a discussion. 

I am +1 on the idea, but a pydev discussion might be needed.

How did you test the patch?  I don't think that passing the same tests in non-verbose mode is good enough, as an empty test is a pass.  What would be convincing is an automated comparison of verbose output before and after that showed that everything run before is run after. There might be more after if something was omitted from a run_unittest call. That past actuality and current possibility is part of the reason for the change.

Timing: I think applying this too close to a release might be a bad idea. I am thinking more of human mental adjustments (and the need to refresh some patches) rather than likely technical issues. If this were approved when 3.4.2 were expected within a month, say, I would wait until it were released.
Date User Action Args
2014-06-13 20:07:36terry.reedysetrecipients: + terry.reedy, ezio.melotti, zach.ware
2014-06-13 20:07:36terry.reedysetmessageid: <>
2014-06-13 20:07:36terry.reedylinkissue21741 messages
2014-06-13 20:07:36terry.reedycreate