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.
Created on 2008年05月07日 21:27 by Rhamphoryncus, last changed 2022年04月11日 14:56 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| python-unittest_flush.diff | Rhamphoryncus, 2008年05月07日 21:27 | |||
| Messages (3) | |||
|---|---|---|---|
| msg66375 - (view) | Author: Adam Olsen (Rhamphoryncus) | Date: 2008年05月07日 21:27 | |
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. |
|||
| msg66376 - (view) | Author: Adam Olsen (Rhamphoryncus) | Date: 2008年05月07日 21:48 | |
Hrm, this behaviour exists in trunk as well. I must be confused about the cause (but the patch still fixes it.) |
|||
| msg66639 - (view) | Author: Georg Brandl (georg.brandl) * (Python committer) | Date: 2008年05月11日 15:17 | |
Thanks, committed patch as r63069. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022年04月11日 14:56:34 | admin | set | github: 47036 |
| 2008年05月11日 15:17:52 | georg.brandl | set | status: open -> closed resolution: accepted messages: + msg66639 nosy: + georg.brandl |
| 2008年05月07日 21:48:23 | Rhamphoryncus | set | messages: + msg66376 |
| 2008年05月07日 21:27:24 | Rhamphoryncus | create | |