Terry J. Reedy <tjre...@udel.edu> added the comment:
Evan, IDLE runs your code with the Python running IDLE. Bad tracebacks are created by Python and are usually, as in this case, the fault of Python. To decide, run your code directly with Python, at a command line, instead of indirectly with IDLE, and see if you get the same problem. In this case, I ran, on Windows, in Command Prompt, 'py -m a.tem3', where 'py' defaults to python 3.7.1 and 'a' is a directory on sys.path. ---------- assignee: terry.reedy -> components: -IDLE stage: -> resolved status: open -> closed _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue35355> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
