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.

Title: Idle: handle 'raise' properly when running with subprocess (2.7)
Type: behavior Stage: resolved
Components: IDLE Versions: Python 2.7
Status: closed Resolution: wont fix
Dependencies: Superseder:
Assigned To: terry.reedy Nosy List: terry.reedy
Priority: low Keywords:

Created on 2015-08-25 16:41 by terry.reedy, last changed 2022-04-11 14:58 by admin. This issue is now closed.

Messages (2)
msg249137 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2015-08-25 16:41
With one process (installed 2.7.10, -n option):
>>> raise
Traceback (most recent call last):
  File "<pyshell#0>", line 2, in <module>
TypeError: exceptions must be old-style classes or derived from BaseException, not NoneType

With subprocess (default option):
>>> raise

Traceback (most recent call last):
** IDLE Internal Exception: 
  File "C:\Programs\Python27\lib\idlelib\", line 325, in runcode
    exec code in self.locals
  File "C:\Programs\Python27\lib\idlelib\", line 111, in main
    seq, request = rpc.request_queue.get(block=True, timeout=0.05)
  File "C:\Programs\Python27\lib\", line 176, in get
    raise Empty

The 2.7.10 says " If no exception is active in the current scope, a TypeError exception is raised indicating that this is an error (if running under IDLE, a Queue.Empty exception is raised instead)."  The comment is not true with -n.  But adding changing 'IDLE' to 'IDLE without -n' might encourage people to think that they should use '-n'.

A workaround fix might be to add a special check to the internal error handling code to print the TypeError instead. I do not know of any other open issues about Internal Exceptions being printed.

This is a low priority issue, but it is peculiar that this seems to be the only exception so mangled. The only issue issue I found related to this section of the Idle code is #1190163.

This is a 2.7 issue only. In 3.4+, console or Idle in either mode:
>>> raise
Traceback (most recent call last):
  File "<pyshell#0>", line 1, in <module>
RuntimeError: No active exception to reraise
msg296377 - (view) Author: Terry J. Reedy (terry.reedy) * (Python committer) Date: 2017-06-19 21:18
The Runtime error is what current py 3 raises.  TypeError is what 2.7.13 raises. Since the only problem is for someone who read the doc running 'raise' in IDLE 2.7  in -n mode, closing.
Date User Action Args
2022-04-11 14:58:20adminsetgithub: 69124
2017-06-19 21:18:55terry.reedysetstatus: open -> closed
messages: + msg296377

assignee: terry.reedy
components: + IDLE
resolution: wont fix
stage: needs patch -> resolved
2015-08-25 16:41:24terry.reedycreate