Changes by Terry J. Reedy tjre...@udel.edu:
--
resolution: - out of date
status: pending - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2657
___
Changes by A.M. Kuchling li...@amk.ca:
--
assignee: akuchling -
status: pending - open
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2657
___
___
Terry J. Reedy tjre...@udel.edu added the comment:
That should be, for 2.7 or 3.2, as 3.1 is nearly finished.
--
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2657
___
Terry J. Reedy tjre...@udel.edu added the comment:
Is this an issue with 2.7 or 3.1?
--
nosy: +tjreedy
status: open - pending
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue2657
___
Fernando Pérez [EMAIL PROTECTED] added the comment:
As reported by Ondrej Certik on the IPython mailing list:
Here is how to reliably (100%) reproduce it in ipython 0.8.2 (the bug
indeed goes away in 0.8.4):
http://code.google.com/p/sympy/issues/detail?id=822
together with a screenshot how
Changes by A.M. Kuchling [EMAIL PROTECTED]:
--
assignee: - akuchling
nosy: +akuchling
title: curses - Curses sometimes fails to initialize terminal
__
Tracker [EMAIL PROTECTED]
http://bugs.python.org/issue2657
__
New submission from Fernando Pérez [EMAIL PROTECTED]:
Curses sometimes fails to correctly initialize the terminal.
Unfortunately I don't know how to reproduce the problem, it was reported
multiple times by ipython users, but I have no idea what causes it. I
finally found a workaround by making
