[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Martin Panter added the comment: Adam: My experiments were assuming that PyOS_Readline() only ever uses the basic implementation or the Readline library, in order to see if there was any consistency with how Python worked in common situations. There is actually a test that waits for the interp

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Adam Bartoš added the comment: > * The interactive interpreter always reads from the original standard input, > whether Readline is used or not. This is not true – the interactive interpreter reads via PyOS_Readline, which may call whatever readline hook is installed. I think the situation wo

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Martin Panter added the comment: Actually Issue 1927 has a simple patch which should change this to stdout. I haven’t tested, the code looks like that patch will not use a redirected sys.stdout, so it would match not using a redirected sys.stdin. -- ___

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Martin Panter added the comment: Results of experimenting on 3.6: * The startup messages are written to standard error. * The interactive interpreter prompts to the original standard error if Readline not used. But with Gnu Readline, prompts do go to the original standard output, as does other

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Drekin added the comment: Related stackoverflow question: http://stackoverflow.com/questions/18419787/where-does-pythons-interactive-prompt-output-to . -- nosy: +Drekin ___ Python tracker

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

Changes by Ezio Melotti : -- components: +Extension Modules type: -> behavior versions: +Python 3.3, Python 3.4 ___ Python tracker ___ __

[issue12869] PyOS_StdioReadline is printing the prompt on stderr

New submission from Albert Zeyer : PyOS_StdioReadline from Parser/myreadline.c is printing the prompt on stderr. I think it should print it on the given parameter sys_stdout. Other readline implementations (like from the readline module) also behave this way. Even if it really is supposed to w