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 roger.serwy
Recipients Ramchandra Apte, loewis, ned.deily, roger.serwy, serhiy.storchaka, terry.reedy
Date 2012-07-11.05:33:40
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1341984822.66.0.85061064922.issue15319@psf.upfronthosting.co.za>
In-reply-to
Content
PyShell.py's PyShell object has the readline method, at line 1080 in the most recent code. It's meant for use with and without a subprocess. (See also Issue14254)

The IDLEfork project long ago created the subprocess and the RPC plumbing for the subprocess interaction with the *existing* PyShell(OutputWindow) object as stdin/stdout/stderr. This RPC, found in rpc.py, is used in run.py and PyShell's ModifiedInterpreter. The start_subprocess method connects the stdin/stdout/stderr from the IDLE front-end to the subprocess in run.py. The stdout/stderr objects are the PyShell(OutputWindow) object wrapped by PseudoFile. Stdin is not wrapped, but it should be.

I know that this issue deals with stdin specifically, but I hope that the additional stdout/stderr information places the problem into a greater context.
History
Date User Action Args
2012-07-11 05:33:43roger.serwysetrecipients: + roger.serwy, loewis, terry.reedy, ned.deily, Ramchandra Apte, serhiy.storchaka
2012-07-11 05:33:42roger.serwysetmessageid: <1341984822.66.0.85061064922.issue15319@psf.upfronthosting.co.za>
2012-07-11 05:33:42roger.serwylinkissue15319 messages
2012-07-11 05:33:40roger.serwycreate