Message 140879 - Python tracker

➜

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	chn
Recipients	Evgeny.Tarasov, alexey-smirnov, chn, neologix, r.david.murray, rosslagerwall, socketpair, vstinner
Date	2011-07-22.13:57:33
SpamBayes Score	3.6205745e-06
Marked as misclassified	No
Message-id	<1311343054.48.0.372460761278.issue12607@psf.upfronthosting.co.za>
In-reply-to

Content
Thanks for the patch, I haven't tried it (I'm still on Python 2.7) but it looks very special-cased to my case. I can think about exotic cases like stdin = sys.stderr, stdout = sys.stdin, stderr = sys.stdout It can happen in reality if a daemon have closed stdio (see bug 10806) and reusing fd's 0,1,2 for other purposes.

Thanks for the patch, I haven't tried it (I'm still on Python 2.7) but it looks very special-cased to my case. I can think about exotic cases like

stdin = sys.stderr, stdout = sys.stdin, stderr = sys.stdout

It can happen in reality if a daemon have closed stdio (see bug 10806) and reusing fd's 0,1,2 for other purposes.

History
Date	User	Action	Args
2011-07-22 13:57:34	chn	set	recipients: + chn, vstinner, r.david.murray, neologix, rosslagerwall, socketpair, alexey-smirnov, Evgeny.Tarasov
2011-07-22 13:57:34	chn	set	messageid: <1311343054.48.0.372460761278.issue12607@psf.upfronthosting.co.za>
2011-07-22 13:57:33	chn	link	issue12607 messages
2011-07-22 13:57:33	chn	create