That does not really resolve the handling of a plain "\r" (cursor should go to the beginning of line and overwrite the previous line with new content). Also, there is urwid and gtk which need a fix.

Original Comment By: Andreas Stührk

What about a workaround trivial like this one?
{{{

--- a/bpython/cli.py Sat Jul 03 14:04:21 2010 +0200
+++ b/bpython/cli.py Sun Jul 04 09:51:11 2010 +0200
@@ -479,6 +479,8 @@
s = s.replace('\x01', '')
# Replace NUL bytes, as addstr raises an exception otherwise
s = s.replace('\x00', '')

•    # Replace \r\n bytes, as addstr remove the current line otherwise
  

•    s = s.replace('\x0D\x0A', '\x0A')
  
   self.scr.addstr(s, a)
  

}}}

Original Comment By: Michele Orrù

This is the behaviour of curses' addstr(), we should probably work around that (in a general way, all our backends behave differently right now).

Original Comment By: Andreas Stührk

The real issue here seems to be that bpython does not like printing lines with a carriage return in it.

E.g.
{{{

print "spam\r\nspam"

spam

}}}

vs.
{{{

print "spam\nspam"
spam
spam

}}}

Original Comment By: Andreas Stührk

oops, reported as anonymous, but 'tis really me!

Original Comment By:

This is no longer an issue in bpython-curses.