Message150703
| Author |
pitrou |
| Recipients |
Arfrever, amaury.forgeotdarc, denilsonsa, giampaolo.rodola, loewis, neologix, pitrou, rosslagerwall, vstinner, zbysz |
| Date |
2012年01月06日.00:26:47 |
| SpamBayes Score |
4.3715193e-07 |
| Marked as misclassified |
No |
| Message-id |
<1325809532.8907.30.camel@localhost.localdomain> |
| In-reply-to |
<1325809170.41.0.294935319431.issue13609@psf.upfronthosting.co.za> |
| Content |
> I don't think that it's possible that stdin, stdout and/or stderr have
> its own terminal. I suppose that the 3 streams are always attached to
> the same terminal. So I don't see why the function would take an
> argument. Tell me if I am wrong.
I think it can be useful in case the program creates its own
session/terminal using openpty?
> Instead of using sys.__stdout__.fileno(), you can directly use 1
> because Python always create sys.__stdout__ from the file descriptor
> 1.
From pythonrun.c:
/* Set sys.stdin */
fd = fileno(stdin);
[...]
/* Set sys.stdout */
fd = fileno(stdout);
[...]
/* Set sys.stderr, replaces the preliminary stderr */
fd = fileno(stderr); |
|