[issue10144] Buffering bug after calling curses function

Changes by Ned Deily : -- resolution: -> wont fix status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue10144] Buffering bug after calling curses function

Fernando Perez added the comment: No problem for us (IPython) if you mark it as won't fix. I've just applied the environment workaround you guys suggested: http://github.com/ipython/ipython/commit/147b245d2ead0e15d2c17b7bb760a03126660fb7 Thanks a lot for that tip! That leaves us in good shap

[issue10144] Buffering bug after calling curses function

Ned Deily added the comment: Thanks for NCURSES_NO_SETBUF ("when it doubt read the man page"!). Since the problem does not seem to exist in python3 and this is likely been an issue for a long time and apparently not previously reported and there are various workarounds, I think this could be

[issue10144] Buffering bug after calling curses function

Andreas Stührk added the comment: That behaviour is indeed caused by ncurses as it changes the buffer size of stdio. The rationale behind that is explained in a comment in ncurses/tinfo/setbuf.c (http://codesearch.google.com/codesearch/p?hl=en#5KTrgOW2hXs/pub/nslu2/sources/ncurses-5.4.tar.gz%

[issue10144] Buffering bug after calling curses function

Ned Deily added the comment: The problem is reproducible with the python2 versions I have access to, that is, on Mac OS X and Debian Linux, and likewise not with any of the python3 3.1 and 3.2 versions. It is most likely due to the underlying ncurses library interacting with the libc stdio,

[issue10144] Buffering bug after calling curses function

New submission from Wes McKinney : We tracked a bug originating in IPython to the Python interpreter itself, seems to be present in 2.6.x and 2.7.x but not 3.1.x. This is on Ubuntu Linux 10.04, does not seem to occur in OS X 10.6. Reference: http://article.gmane.org/gmane.comp.python.ipython.u