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 | Rhamphoryncus |
|---|---|
| Recipients | Rhamphoryncus |
| Date | 2008年05月07日.21:27:17 |
| SpamBayes Score | 0.003311624 |
| Marked as misclassified | No |
| Message-id | <1210195645.66.0.390222470388.issue2787@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
In 3.0, unittest's output has become line buffered. Instead of printing the test name when it starts a test, then "ok" when it finishes, the test name is delayed until the "ok" is printed. This makes it unnecessarily hard to determine which test is hanging or segfaulted. The attached patch adds explicit flushes. An alternative approach would be to force stdout to be unbuffered somehow. I don't know how difficult that would be. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年05月07日 21:27:27 | Rhamphoryncus | set | spambayes_score: 0.00331162 -> 0.003311624 recipients: + Rhamphoryncus |
| 2008年05月07日 21:27:26 | Rhamphoryncus | set | spambayes_score: 0.00331162 -> 0.00331162 messageid: <1210195645.66.0.390222470388.issue2787@psf.upfronthosting.co.za> |
| 2008年05月07日 21:27:24 | Rhamphoryncus | link | issue2787 messages |
| 2008年05月07日 21:27:23 | Rhamphoryncus | create | |