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

Changes by Berker Peksag : -- stage: test needed -> resolved status: open -> closed ___ Python tracker ___ ___ Python-bugs-list mailing

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

Changes by Serhiy Storchaka : -- nosy: +serhiy.storchaka ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https:/

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

Brian Harring added the comment: This change isn't hugely friendly API wise- for code that invokes setupterm() multiple items (and does so knowing what it's doing), they're now silently locked into whatever the first term invocation was. Personally, an override here has major usage- especiall

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

Barry A. Warsaw added the comment: Doko asks in IRC to apply this for 2.6.6. Approved. -- nosy: +barry status: pending -> open ___ Python tracker ___ ___

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

Matthias Klose added the comment: committed in r83306 (2.7) and r83307 (3.2); verified that the behaviour in offlineimap (reported in http://bugs.debian.org/586433 is fixed). will apply it to 2.6 and 3.1 after a few days. -- resolution: -> fixed status: open -> pending versions: +Pyth

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

Matthias Klose added the comment: shouldn't `initialised_setupterm' be tested instead? -- nosy: +doko ___ Python tracker ___ ___ Pytho

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

Sreejith Madhavan added the comment: Thanks for the patch. I can confirm that the patch works for 64bit builds of python-2.6.5 on Solaris (amd64 and sparc) and RHEL5 amd64. The curses library used was ncurses-5.7 with widechar support. -- nosy: +Sreejith.Madhavan

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

Changes by Brian Curtin : -- keywords: +needs review priority: -> normal stage: -> test needed type: -> behavior ___ Python tracker ___

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

Changes by Sami Zerrade : Added file: http://bugs.python.org/file16055/setupterm.patch ___ Python tracker ___ ___ Python-bugs-list mailing list

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

Changes by Sami Zerrade : Removed file: http://bugs.python.org/file16054/setupterm.patch ___ Python tracker ___ ___ Python-bugs-list mailing li

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

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/file16054/setup

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

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 behavior from version 2.5.

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

New submission from Yury : Calling curses.initscr after curses.endwin() results in a messed up terminal the second time curses.endwind() is called. For example: import curses curses.initscr(); curses.endwin(); curses.initscr(); curses.endwin() This behaves correctly in python 2.5. It does not w