[issue984870] curses: getmaxyx() breaks when the window shrinks

2014-04-15 Thread A.M. Kuchling
A.M. Kuchling added the comment: I agree with Chris's logic; the incorrect size seems to be a curses/ncurses bug that has gotten fixed somewhere along the line. You also aren't able to shrink the terminal to be smaller than the size of a derived window created with derwin(), but you seem to

[issue984870] curses: getmaxyx() breaks when the window shrinks

2014-04-14 Thread Christian Hudon
Christian Hudon added the comment: I get the same traceback. The traceback happens only when the window is shrunk below the size specified in derwin(). It's easy to see this by changing the first and second arguments to the derwin call to something like 2, 2, and then you can resize the

[issue984870] curses: getmaxyx() breaks when the window shrinks

2011-04-17 Thread akira
akira 4kir4...@gmail.com added the comment: The test produces a traceback while shrinking a window (increasing the window size works ok): Traceback (most recent call last): File screen-resize-bug-curses.py, line 22, in module curses.wrapper(main) File /.../python2.7/curses/wrapper.py,

[issue984870] curses: getmaxyx() breaks when the window shrinks

2010-08-19 Thread Mark Lawrence
Changes by Mark Lawrence breamore...@yahoo.co.uk: -- versions: +Python 2.7, Python 3.1, Python 3.2 -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue984870 ___

[issue984870] curses: getmaxyx() breaks when the window shrinks

2009-02-14 Thread Daniel Diniz
Daniel Diniz aja...@gmail.com added the comment: I get a different behavior, with shrinking reporting correct sizes, but quiting with a _curses.error: curses function returned NULL, on trunk, KDE 3.5's Konsole._curses.error: curses function returned NULL -- nosy: +ajaksu2 stage: - test