In my project (OOF, Object Oriented Finite Elements, http://www.ctcms.nist.gov/oof), we have gotten complaints from Ubuntu users, which we have traced to this bug. We use a "w=curses.initscr(); s=w.getxymax(); curses.endwin()" sequence to get the screen width for drawing text-mode progress bars, which we do multiple times, because the screen width might have changed. Also, our test suite uses these text-mode progress bars, and fails on Ubuntu because of this bug.
We have worked around it by only checking the screen width once, and assuming/hoping it doesn't change.
The bug is present in python2.6 package version 2.6.2-0ubuntu1 (ships with 9.04 "Jaunty") and 2.6.4-0ubuntu3 (ships with 9.10 "Karmic").
In my project (OOF, Object Oriented Finite Elements, http:// www.ctcms. nist.gov/ oof), we have gotten complaints from Ubuntu users, which we have traced to this bug. We use a "w=curses. initscr( ); s=w.getxymax(); curses.endwin()" sequence to get the screen width for drawing text-mode progress bars, which we do multiple times, because the screen width might have changed. Also, our test suite uses these text-mode progress bars, and fails on Ubuntu because of this bug.
We have worked around it by only checking the screen width once, and assuming/hoping it doesn't change.
The bug is present in python2.6 package version 2.6.2-0ubuntu1 (ships with 9.04 "Jaunty") and 2.6.4-0ubuntu3 (ships with 9.10 "Karmic").