Message127773
| Author |
belopolsky |
| Recipients |
amaury.forgeotdarc, belopolsky, benjamin.peterson, doko, naufraghi, petere, pitrou, stutzbach |
| Date |
2011年02月02日.22:25:30 |
| SpamBayes Score |
5.4933757e-08 |
| Marked as misclassified |
No |
| Message-id |
<1296685531.24.0.409974950135.issue7111@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
> If we want to allow for closed {stdin, stdout, stderr}, I'm not sure
> what the semantics should be. Should sys.std{in, out, err} be None? Or a
> file object which always throws an error?
I would say it should be a *pseudo*-file object which always throws a *descriptive* error. Note that setting sys.stdout to None makes print() do nothing rather than report an error:
>>> sys.stdout = None
>>> print('abc')
See also issue6501. |
|