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 filip.zyzniewski
Recipients filip.zyzniewski, neologix
Date 2012-12-07.14:08:03
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1354889283.34.0.359637854781.issue16635@psf.upfronthosting.co.za>
In-reply-to
Content
If stdout was closed before closing stderr, then stdout problems could be reported, and that is what I would expect when using Python this way.

os.fsync(1) helps, but only if preceeded by sys.stdout.flush() and it seems a bit cumbersome.

Is there any downside to doing close(1) explicitely?

cat, grep, dd and echo close their stdout, why couldn't Python do this?
History
Date User Action Args
2012-12-07 14:08:03filip.zyzniewskisetrecipients: + filip.zyzniewski, neologix
2012-12-07 14:08:03filip.zyzniewskisetmessageid: <1354889283.34.0.359637854781.issue16635@psf.upfronthosting.co.za>
2012-12-07 14:08:03filip.zyzniewskilinkissue16635 messages
2012-12-07 14:08:03filip.zyzniewskicreate