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 Kevin.Barry
Recipients Kevin.Barry, emmanuel, vstinner
Date 2013-03-24.16:47:35
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>

Regarding your points: All three can be taken care of with a combination of my patch and setting sys.stdin, sys.stdout, and sys.stderr to the pty. (That should really be done internally with another patch, since os.fdopen is OS-specific. Also, sys.stdin, sys.stdout, and sys.stderr should each have distinct underlying file descriptors, which I didn't do in working.c.) Those can safely be replaced since they're just the "effective" standard files, and sys.__stdin__ et al. refer to the actual C stdin et al. The remaining issue would be that the same descriptor shouldn't be used for both input and output in the interpreter loop, especially if the FILE* passed is only open for reading (since standard input technically doesn't have to be writable.)

Kevin Barry
Date User Action Args
2013-03-24 16:47:36Kevin.Barrysetrecipients: + Kevin.Barry, vstinner, emmanuel
2013-03-24 16:47:35Kevin.Barrysetmessageid: <>
2013-03-24 16:47:35Kevin.Barrylinkissue14916 messages
2013-03-24 16:47:35Kevin.Barrycreate