[issue29616] input() after restarting causes bug

Changes by Terry J. Reedy : -- resolution: -> works for me stage: -> resolved status: pending -> closed ___ Python tracker ___

[issue29616] input() after restarting causes bug

Changes by Serhiy Storchaka : -- status: open -> pending ___ Python tracker ___

[issue29616] input() after restarting causes bug

Serhiy Storchaka added the comment: The implementation of standard input/output in IDLE was significantly changed in recent years. -- ___ Python tracker

[issue29616] input() after restarting causes bug

Terry J. Reedy added the comment: Characters typed before Enter are never sent the the execution process, so there are not even interpreted as a string, let alone a command. Do you see exactly the following when you start IDLE? Python 3.6.0 (v3.6.0:41df79263a11, Dec 23 2016, 08:06:12) [MSC

[issue29616] input() after restarting causes bug

Juan added the comment: I am using Windows 10 64-bit. >> sometimes whatever you pressed in step 3 disappears, > > When Shell is restarted by whatever means, any pending input, whether in > response to '>>>' or user input(), is cancelled and > *should* disappear and not be left to look as if it

[issue29616] input() after restarting causes bug

Terry J. Reedy added the comment: What OS are you using? > 6. Bug. This does not tell me what you think the bug is. > sometimes whatever you pressed in step 3 disappears, When Shell is restarted by whatever means, any pending input, whether in response to '>>>' or user input(), is cancelled

[issue29616] input() after restarting causes bug

Juan added the comment: *doesn't respond to commands. I mean something similar to (not equal) "while(1): pass") -- ___ Python tracker ___

[issue29616] input() after restarting causes bug

Juan added the comment: What I meant was: 1. Open a file whose content is "input()" with IDLE 2. F5 3. Type something but without pressing Enter. 4. Come back to the script (with input() still responding to keystrokes on the input line) 5. F5 6. Bug. (Results vary even on the same machine by

[issue29616] input() after restarting causes bug

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka status: open -> pending ___ Python tracker ___

[issue29616] input() after restarting causes bug

Terry J. Reedy added the comment: I am not sure what you mean by 'this bug'. I presume by 'take input' you mean 'display keystrokes on the input line'. If so, the behavior you describe for 3.6 is the correct behavior and not a bug: accept kestrokes until 'Enter' is pressed or until the

[issue29616] input() after restarting causes bug

New submission from Juan: This bug can be recreated by opening a file whose content is "input()" with IDLE, press F5 and the shell opens as expected. Without making the input in the shell stop, press F5 in the script again. In Python 3.5 IDLE only take input until another F5 (or Ctrl+F6) in