[issue7567] Messed up terminal after calling curses.initscr() twice.

2010-01-30 Thread Sami Zerrade
Changes by Sami Zerrade : Added file: http://bugs.python.org/file16055/setupterm.patch ___ Python tracker <http://bugs.python.org/issue7567> ___ ___ Python-bugs-list m

[issue7567] Messed up terminal after calling curses.initscr() twice.

2010-01-30 Thread Sami Zerrade
Changes by Sami Zerrade : Removed file: http://bugs.python.org/file16054/setupterm.patch ___ Python tracker <http://bugs.python.org/issue7567> ___ ___ Python-bugs-list m

[issue7567] Messed up terminal after calling curses.initscr() twice.

2010-01-30 Thread Sami Zerrade
Sami Zerrade added the comment: I'm attaching a file that patches Modules/_cursesmodule.c to make sure that initscr hasn't been called before invoking setupterm(). This fixes the bug for me; your mileage may vary. -- keywords: +patch Added file: http://bugs.python.org

[issue7567] Messed up terminal after calling curses.initscr() twice.

2010-01-30 Thread Sami Zerrade
Sami Zerrade added the comment: This is being caused by the following 2 new lines in the initscr() function of Lib/curses/__init__.py: setupterm(term=_os.environ.get("TERM", "unknown"), fd=_sys.__stdout__.fileno()) Commenting them out will cause the behav