[Python-bugs-list] [ python-Bugs-665570 ] curses causes interpreter crash

SourceForge.net noreply@sourceforge.net
Sun, 12 Jan 2003 07:00:24 -0800


Bugs item #665570, was opened at 2003-01-10 04:34
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=665570&group_id=5470

Category: Python Library
>Group: 3rd Party
>Status: Closed
>Resolution: Invalid
Priority: 5
Submitted By: Matthias Klose (doko)
>Assigned to: Neal Norwitz (nnorwitz)
Summary: curses causes interpreter crash

Initial Comment:
[submitted to http://bugs.debian.org/175589 ]

A call to curses.initscr() that fails because of an
error (such as TERM not being set) causes the program
to exit.  No exception thrown, no error returned -- an
EXIT.  There is very anti-Pythonic and, at minimum,
should be documented.


----------------------------------------------------------------------

>Comment By: Neal Norwitz (nnorwitz)
Date: 2003-01-12 10:00

Message:
Logged In: YES 
user_id=33168

I do not believe this is a bug in python.  The exit is
occuring in initscr() in libncurses:

#0  exit (status=1) at exit.c:40
#1  0x40289b62 in initscr () from /usr/lib/libncurses.so.5
#2  0x402417f1 in PyCurses_InitScr (self=0x0)

We have no control over this problem.  
I have documented that the interpreter can exit in
Doc/lib/libcurses.tex 1.41and 1.37.6.2.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=665570&group_id=5470