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 belopolsky
Recipients amaury.forgeotdarc, belopolsky, benjamin.peterson, doko, naufraghi, petere, pitrou, stutzbach
Date 2011-02-02.22:25:30
SpamBayes Score 5.49338e-08
Marked as misclassified No
Message-id <>
> 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.
Date User Action Args
2011-02-02 22:25:31belopolskysetrecipients: + belopolsky, doko, amaury.forgeotdarc, pitrou, benjamin.peterson, stutzbach, naufraghi, petere
2011-02-02 22:25:31belopolskysetmessageid: <>
2011-02-02 22:25:30belopolskylinkissue7111 messages
2011-02-02 22:25:30belopolskycreate