[issue5622] wrong error from curses.wrapper if curses initialization fails

2011-03-09 Thread Roundup Robot
Roundup Robot devnull@devnull added the comment: New changeset c731e02472c5 by Ned Deily in branch '2.7': Issue #5622: Fix curses.wrapper to raise correct exception if curses http://hg.python.org/cpython/rev/c731e02472c5 -- nosy: +python-dev ___

[issue5622] wrong error from curses.wrapper if curses initialization fails

2011-03-09 Thread Roundup Robot
Roundup Robot devnull@devnull added the comment: New changeset 6b6b8af33811 by Ned Deily in branch '3.1': Issue #5622: Fix curses.wrapper to raise correct exception if curses http://hg.python.org/cpython/rev/6b6b8af33811 New changeset e6c45cd46cb2 by Ned Deily in branch '3.2': Issue #5622:

[issue5622] wrong error from curses.wrapper if curses initialization fails

2011-03-09 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- assignee: - ned.deily resolution: - fixed stage: patch review - committed/rejected status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5622

[issue5622] wrong error from curses.wrapper if curses initialization fails

2011-01-08 Thread Ned Deily
Ned Deily n...@acm.org added the comment: A simpler way to reproduce: TERM= python -c 'import curses; curses.wrapper(lambda a:a.getch())' I looked at adding an automated test case for this but it is a little tricky to make it bulletproof across all environments. Since the problem is really a

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-11-20 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- keywords: +easy nosy: -BreamoreBoy stage: unit test needed - patch review versions: -Python 2.6 ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5622 ___

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-11-20 Thread Ned Deily
Changes by Ned Deily n...@acm.org: Removed file: http://bugs.python.org/file18285/issue5622.diff ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5622 ___

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-08-16 Thread Freek Dijkstra
Freek Dijkstra fr...@macfreek.nl added the comment: I can confirm that both the problem exists and the patch works on Python 2.6 and 3.1. I love to see it committed. -- nosy: +macfreek ___ Python tracker rep...@bugs.python.org

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-07-31 Thread Mark Lawrence
Mark Lawrence breamore...@yahoo.co.uk added the comment: This is a one line patch on wrapper.py. Sorry I can't do any more with this cos I only have a windows box. -- keywords: +patch nosy: +BreamoreBoy stage: - unit test needed type: - behavior versions: +Python 3.2 -Python 3.0

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-07-31 Thread Ned Deily
Ned Deily n...@acm.org added the comment: [FYI: Comments at the beginning of a patch file are ignored by the standard Unix-y patch utilities. They are there for a reason.] -- ___ Python tracker rep...@bugs.python.org

[issue5622] wrong error from curses.wrapper if curses initialization fails

2010-07-31 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- nosy: +akuchling ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue5622 ___ ___ Python-bugs-list mailing list

[issue5622] wrong error from curses.wrapper if curses initialization fails

2009-03-31 Thread Ned Deily
New submission from Ned Deily n...@acm.org: wrong error from curses.wrapper if curses initialization fails One way to reproduce is trying under IDLE.app in OS X: import curses def scr(a): a.getch() curses.wrapper(scr) Traceback before patch: UnboundLocalError: local variable