New submission from Tadhg McDonald-Jensen: (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. ---------- components: IDLE files: run.py messages: 262293 nosy: Tadhg McDonald-Jensen priority: normal severity: normal status: open title: IDLE incorrectly labeling error as internal type: behavior versions: Python 2.7, Python 3.5 Added file: http://bugs.python.org/file42261/run.py _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue26627> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com