[issue12833] raw_input misbehaves when readline is imported

Martin Panter added the comment: I wonder if this information would be better off under the input() function, rather than under the Readline module itself. Also see Issue 17337, about control codes in the Readline prompt. Since these issues both relate to the prompt, it might be worth document

[issue12833] raw_input misbehaves when readline is imported

Berker Peksag added the comment: Also, I'd change the patch to use a note directive. -- nosy: +berker.peksag stage: commit review -> patch review ___ Python tracker ___ _

[issue12833] raw_input misbehaves when readline is imported

Martin Panter added the comment: Actually, there should either be a space before the double-colons, or the full stops should be removed. So either of these options: . . . when a backspace is typed. :: . . . when a backspace is typed:: -- ___ Python

[issue12833] raw_input misbehaves when readline is imported

Martin Panter added the comment: The patch looks find for Python 3. The sample code should probably be adapted to raw_input() for Python 2. -- nosy: +vadmium stage: needs patch -> commit review versions: +Python 3.4, Python 3.5, Python 3.6 -Python 3.2, Python 3.3 __

[issue12833] raw_input misbehaves when readline is imported

Dhanam Prakash added the comment: Hi, submitting a patch for the documentation. Thanks -- hgrepos: +254 keywords: +patch nosy: +dhanamp Added file: http://bugs.python.org/file35519/issue12833.patch ___ Python tracker

[issue12833] raw_input misbehaves when readline is imported

Éric Araujo added the comment: > Still, this behavior is surprising and undesirable. I would suggest > adding a note to the docs for the readline module +1. -- assignee: -> docs@python components: +Documentation -IO, Interpreter Core nosy: +docs@python stage: test needed -> needs patch

[issue12833] raw_input misbehaves when readline is imported

Idan Kamara added the comment: You're right, as this little C program verifies: #include #include #include int main() { printf("foo "); char* buf = readline(""); free(buf); return 0; } Passing ' ' seems to be a suitable workaround for those who can't pass the text directly to

[issue12833] raw_input misbehaves when readline is imported

Nadeem Vawda added the comment: Reproduced on 3.3 head. Looking at the documentation of the C readline library, it needs to know the length of the prompt in order to display properly, so this seems to be an acknowledged limitation of the underlying library rather than a bug on our side. Still,

[issue12833] raw_input misbehaves when readline is imported

Idan Kamara added the comment: Reproduced on 2.7. (flushing stdin/out doesn't help) -- versions: +Python 2.7 ___ Python tracker ___

[issue12833] raw_input misbehaves when readline is imported

Éric Araujo added the comment: Maybe you need to call sys.stdin.flush() before raw_input? In any way, 2.6 is in security mode, so we need to reproduce this with current versions: 2.7, 3.2 or 3.3. -- components: +IO, Interpreter Core -Library (Lib) nosy: +eric.araujo, pitrou stage: ->

[issue12833] raw_input misbehaves when readline is imported

Changes by Mads Kiilerich : -- nosy: +kiilerix ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.pyth

[issue12833] raw_input misbehaves when readline is imported

New submission from Idan Kamara : import sys, readline sys.stdout.write('foo ') raw_input() When trying the above on Debian, 2.6.6 using gnome-terminal, typing a character then hitting backspace deletes "foo " as well. I'm not sure if this is a bug or the expected behavior when writing to std