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, roger.serwy, terry.reedy
Date 2011-12-24.04:36:02
SpamBayes Score 4.0012654e-07
Marked as misclassified No
Message-id <1324701363.75.0.115399066917.issue13657@psf.upfronthosting.co.za>
In-reply-to
Content
> Is that sensibly possible? Any line of code can change those, so IDLE would have to do the equivalent of idle.ps1,idle.ps2 = sys.ps1, sys.ps2 before every new ps1 statement prompt.

It may be possible if the code gets refactored such that the subprocess handles the prompt and has stdin/stdout/stderr through RPCProxy treat the PyShell text widget as a dumb terminal.

> I would rather remove the prompts from the entry window itself, and use 4 char indents instead of 8, so that cutting does not pick up the prompts.  IDLE does not have to exactly imitate the Command Window interface. It could also give the user a choice.

This is #11838 and #1178.
History
Date User Action Args
2011-12-24 04:36:03roger.serwysetrecipients: + roger.serwy, terry.reedy, Ramchandra Apte
2011-12-24 04:36:03roger.serwysetmessageid: <1324701363.75.0.115399066917.issue13657@psf.upfronthosting.co.za>
2011-12-24 04:36:03roger.serwylinkissue13657 messages
2011-12-24 04:36:02roger.serwycreate