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 vstinner
Recipients martin.panter, neologix, serhiy.storchaka, vstinner
Date 2015-03-03.12:08:43
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1425384523.38.0.411095115311.issue23570@psf.upfronthosting.co.za>
In-reply-to
Content
New patch to fix the bug seen by Serhiy.

> Anyway, we closed all pipes

Oh, I forgot to explain that TextIOWrapper.close() closes the buffered file even if flush() raised an exception. BufferedWriter.close() does the same.

So stdin.close() always closes the text (binary or text, buffered or not). It's not more possible to use stdin after stdin.close(), even if stdin.close() raised an exception.
History
Date User Action Args
2015-03-03 12:08:43vstinnersetrecipients: + vstinner, neologix, martin.panter, serhiy.storchaka
2015-03-03 12:08:43vstinnersetmessageid: <1425384523.38.0.411095115311.issue23570@psf.upfronthosting.co.za>
2015-03-03 12:08:43vstinnerlinkissue23570 messages
2015-03-03 12:08:43vstinnercreate