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 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 <>
> 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);
Date User Action Args
2012-01-06 00:26:48pitrousetrecipients: + pitrou, loewis, amaury.forgeotdarc, vstinner, giampaolo.rodola, Arfrever, zbysz, denilsonsa, neologix, rosslagerwall
2012-01-06 00:26:47pitroulinkissue13609 messages
2012-01-06 00:26:47pitroucreate