[ python-Bugs-1063840 ] IDLE aborts on any error when started with "-n"

[SourceForge.net]

Bugs item #1063840, was opened at 2004-11-10 09:31
Message generated for change (Comment added) made by kbk
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1063840&group_id=5470

Category: IDLE
Group: Python 2.4
>Status: Closed
>Resolution: Fixed
Priority: 6
Submitted By: Miki Tebeka (tebeka)
Assigned to: Kurt B. Kaiser (kbk)
Summary: IDLE aborts on any error when started with "-n"

Initial Comment:
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)

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

>Comment By: Kurt B. Kaiser (kbk)
Date: 2004-11-13 16:09

Message:
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.

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

Comment By: Miki Tebeka (tebeka)
Date: 2004-11-11 01:45

Message:
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.

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

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