Running Python Script input() method

[GoogleCodeExporter]

When you run a python script, any input(string) statements are executed with 
a dialog input box, which makes all the new lines and things messed up. I 
think it would be better to leave it normal, because I always have to use 
command prompt to test it now if I want to see what it should be displaying.

Original issue reported on code.google.com by mk12...@gmail.com on 18 Jun 2009 at 10:40

[GoogleCodeExporter]

This is a killer issue, and so far is the only reason that I cannot use 
PyScripter
for work. The application I'm debugging has one thread that loops calls to 
raw_input
for commands, while the rest run. It appears that the rest of the threads halt 
when
the dialog pops up. Even if not, the output is suspended while the dialog is 
there,
killing the viability of PyScripter for me.

Original comment by circuits...@gmail.com on 16 Jan 2010 at 12:19

[GoogleCodeExporter]

So what would be the best way in your opinion to handle input()?  Just like the
Python prompt?

Original comment by pyscripter on 18 Jan 2010 at 1:21

[GoogleCodeExporter]

Functionally, yes. The easiest way to implement that, however, is probably to
completely ignore input() and raw_input(). Just redirect sys.stdin, sys.stdout, 
and
sys.stderr across the rpyc channel. Or, better yet, figure out how Idle does it 
and
duplicate it. Idle works extremely well for execution, but falls on its face as 
an
editor.

Original comment by circuits...@gmail.com on 18 Jan 2010 at 8:44

[GoogleCodeExporter]

I would also prefer the normal Python behaviour without message box

Original comment by mproel...@googlemail.com on 1 Aug 2010 at 1:05

[GoogleCodeExporter]

For what it's worth, I also think input without the message box is better.  The 
flow of the interaction sequence works better when the input and output follow 
each other.

Original comment by crc1...@gmail.com on 8 Aug 2010 at 8:59

[GoogleCodeExporter]

I strongly prefer the normal Python behavior without message box

Original comment by basem.al...@gmail.com on 29 Oct 2010 at 10:53

[GoogleCodeExporter]

input without the message box is better, if you want a message box use tkinter.

Original comment by alex.li...@gmail.com on 27 Dec 2010 at 3:35

[GoogleCodeExporter]

I like the dialog box.  And for typical prompt-input-output sequences I have 
taken to sending the output to the next iteration's prompt, so that you see the 
result of the last cycle in the current input dialog box. 

But I appreciate that there are other modes of usage.  Why not make this a 
configuration option, perhaps even one that defaults to "classic" Python input 
behaviour?

Original comment by cspwc...@gmail.com on 30 Jan 2011 at 6:23

[GoogleCodeExporter]

I don't mind the input box, but i can see been a problem for other people, i 
always liked the way IDLE handles it, very C-like

Original comment by guillerm...@gmail.com on 6 May 2011 at 10:44

[GoogleCodeExporter]

I also prefer the normal input without a message box.

Original comment by serw...@gmail.com on 4 Nov 2011 at 12:46

[GoogleCodeExporter]

has their been any movement on this issue?  I love pyscripter, and use it above 
other programs,  but I can't stand input() especially since some modules (pdb) 
prompt for user input quite regularly it's hard to see the difference between 
the pdb prompt and my user input prompt in addition to not being able to tinker 
around with the code/scroll up in the interpreter... meh (ranting about 
freeware, sorry - got frustrated lol).  But!  Any updates?  I'm not seeing any 
options for this in the IDE panel.  

Original comment by jrc.c...@gmail.com on 22 Dec 2011 at 10:01

[GoogleCodeExporter]

Original comment by pyscripter on 7 Mar 2012 at 2:54

• Changed state: Accepted

[GoogleCodeExporter]

Congrats for this IDE! Keep up with the good work! And yes, it would be nice to 
have the standard IDLE-like input() prompt. Or at least, disable the modal for 
the dialog.

Original comment by nelsoj...@gmail.com on 16 Jul 2012 at 8:03

[GoogleCodeExporter]

I too, find that input() is better without the message box. Any plans on 
changing that ? (maybe make it an option for those who prefer it with the 
message box?)

Original comment by williamj...@gmail.com on 24 Sep 2012 at 10:31

[GoogleCodeExporter]

I like the idea of having the message box, but in some cases a input function 
WITH OUT the message box will be 100 times better. How about a option to switch 
between console input and message box input?

Original comment by jonathan...@gmail.com on 22 Oct 2012 at 4:30

[GoogleCodeExporter]

1. I don't like the input dialog message box. Please remove it and keep the way 
as is.
2. It is terrible worse when I found what I input disappeared in the 
interpreter. Please remain the input contents in the interpreter.

Original comment by dingwe...@gmail.com on 26 Oct 2012 at 9:24

[GoogleCodeExporter]

This really needs to be fixed.

Original comment by aidant...@gmail.com on 7 Mar 2013 at 5:22

[GoogleCodeExporter]

Nobody seems to care about what's been said here. I swear bad words every time 
I use input() or pdb.set_trace() or code.interact() in pyscripter. This is the 
only reason I always switch back to IDLE from time to time.

Original comment by imyuanj...@gmail.com on 6 May 2013 at 5:57

[GoogleCodeExporter]

Can someone please address this? There are many people who want input to be 
displayed in the interpreter pane, not a dialog box. Please make an option to 
do this!

Original comment by TheMattM...@gmail.com on 24 May 2014 at 11:36

[GoogleCodeExporter]

Since i enabled the autocomplete of Notepad++, i forgot about PyScripter.

The NppExec plugin is the critical part. Simply hit F6 while working on a .py 
file, and select or save this script (for Python 3.2):

NPP_SAVE
CD $(CURRENT_DIRECTORY)
C:\Python32\python.exe -u "$(FULL_CURRENT_PATH)"

Original comment by CTimmerm...@gmail.com on 3 Jun 2014 at 7:24