classification
Title: IDLE aborts on any error when started with "-n"
Type: Stage:
Components: IDLE Versions: Python 2.4
process
Status: closed Resolution: fixed
Dependencies: Superseder:
Assigned To: kbk Nosy List: kbk, tebeka (2)
Priority: high Keywords

Created on 2004-11-10 14:31 by tebeka, last changed 2004-11-13 21:09 by kbk.

Messages (3)
msg23081 - (view) Author: Miki Tebeka (tebeka) Date: 2004-11-10 14:31 
C:\apps\Python24>python.exe Lib\idlelib\idle.pyw -n

Write: a
An error trace is shown (since "a" is not defined)
and IDLE aborts (closes).

Python 2.4b2, winXP (sp2)
for win32 python and cygwin Python.

(I can't check without the "-n" switch since the
anti-virus blocks the socket connection)
msg23082 - (view) Author: Miki Tebeka (tebeka) Date: 2004-11-11 06:45 
Logged In: YES 
user_id=358087

Checked it on Linux (RH) as well. Whe IDLE starts normally
it works fine and catches the name error. When started with
-n it shows a traceback and closes.
msg23083 - (view) Author: Kurt B. Kaiser (kbk) Date: 2004-11-13 21:09 
Logged In: YES 
user_id=149084

Thanks for the report.

The change in the linecache.checkcache() signature at rev 1.13 caused 
IDLE to exit when an exception was raised while running w/o the 
subprocess.  PyShell rev 1.92.

If the linecache.py change is backported to 2.3 this change must
also be backported.
History
Date User Action Args
2004-11-10 14:31:33tebekacreate