➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

classification
Title: curses causes interpreter crash
Type: Stage:
Components: Library (Lib) Versions:
process
Status: closed Resolution: not a bug
Dependencies: Superseder:
Assigned To: nnorwitz Nosy List: doko, nnorwitz
Priority: normal Keywords:

Created on 2003-01-10 09:34 by doko, last changed 2022-04-10 16:06 by admin. This issue is now closed.

Messages (2)
msg13970 - (view) Author: Matthias Klose (doko) * (Python committer) Date: 2003-01-10 09:34 
[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.
msg13971 - (view) Author: Neal Norwitz (nnorwitz) * (Python committer) Date: 2003-01-12 15:00 
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.
History
Date User Action Args
2022-04-10 16:06:07adminsetgithub: 37752
2003-01-10 09:34:17dokocreate