Message136103
| Author | vstinner |
|---|---|
| Recipients | vstinner |
| Date | 2011-05-16.15:14:03 |
| SpamBayes Score | 0.0026761543 |
| Marked as misclassified | No |
| Message-id | <1305558844.58.0.490167239537.issue12089@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
In Python 3.1, a test fails if it writes to stdout/stderr. It is no more the case in Python 3.2 and 3.3. Why? If we decided to not check for unexpected output in Python 3.2+, the following code should be removed:
if verbose:
capture_stdout = None
else:
capture_stdout = io.StringIO() |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011-05-16 15:14:04 | vstinner | set | recipients: + vstinner |
| 2011-05-16 15:14:04 | vstinner | set | messageid: <1305558844.58.0.490167239537.issue12089@psf.upfronthosting.co.za> |
| 2011-05-16 15:14:03 | vstinner | link | issue12089 messages |
| 2011-05-16 15:14:03 | vstinner | create | |