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 | python-dev |
|---|---|
| Recipients | Ronny.Pfannschmidt, georg.brandl, mkc, pitrou, python-dev, terry.reedy |
| Date | 2011年11月26日.21:11:58 |
| SpamBayes Score | 0.005748641 |
| Marked as misclassified | No |
| Message-id | <E1RUPXR-0000Ci-Pv@dinsdale.python.org> |
| In-reply-to |
| Content | |
|---|---|
New changeset 150e096095e5 by Antoine Pitrou in branch '3.2': Issue #13444: When stdout has been closed explicitly, we should not attempt to flush it at shutdown and print an error. http://hg.python.org/cpython/rev/150e096095e5 New changeset 37300a1df7d7 by Antoine Pitrou in branch 'default': Issue #13444: When stdout has been closed explicitly, we should not attempt to flush it at shutdown and print an error. http://hg.python.org/cpython/rev/37300a1df7d7 |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2011年11月26日 21:11:59 | python-dev | set | recipients: + python-dev, georg.brandl, terry.reedy, mkc, pitrou, Ronny.Pfannschmidt |
| 2011年11月26日 21:11:58 | python-dev | link | issue13444 messages |
| 2011年11月26日 21:11:58 | python-dev | create | |