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.

Author Tadhg McDonald-Jensen
Recipients Tadhg McDonald-Jensen
Date 2016-03-23.18:00:45
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458756045.86.0.656079576242.issue26627@psf.upfronthosting.co.za>
In-reply-to
Content
(I apologize if I'm doing something wrong)

When using a file named run.py in idle, any errors raised from the module makes IDLE show a traceback like this:

Traceback (most recent call last):
** IDLE Internal Exception: 
  File "/Library/Frameworks/Python.framework/Versions/3.5/lib/python3.5/idlelib/run.py", line 351, in runcode
    exec(code, self.locals)
  File "/Users/Tadhg/Documents/run.py", line 1, in <module>
    raise ValueError
ValueError

I looked into idlelib.run and think the culprit is the way print_exception tries to exclude internal files, specifically line 180 in vs 2.7 and line 206 in vs3.5

            exclude = ("run.py", "rpc.py", "threading.py", "queue.py",
                       "RemoteDebugger.py", "bdb.py")

this excludes paths with these names anywhere in the path (later in cleanup_traceback) instead of getting the absolute paths of these modules.
History
Date User Action Args
2016-03-23 18:00:45Tadhg McDonald-Jensensetrecipients: + Tadhg McDonald-Jensen
2016-03-23 18:00:45Tadhg McDonald-Jensensetmessageid: <1458756045.86.0.656079576242.issue26627@psf.upfronthosting.co.za>
2016-03-23 18:00:45Tadhg McDonald-Jensenlinkissue26627 messages
2016-03-23 18:00:45Tadhg McDonald-Jensencreate