[issue16855] traceback module leaves off module name in last line of formatted tracebacks

Irit Katriel added the comment: This is a python 2 only issue. -- nosy: +iritkatriel resolution: -> out of date stage: -> resolved status: open -> closed ___ Python tracker

[issue16855] traceback module leaves off module name in last line of formatted tracebacks

Walter Mundt added the comment: Thanks for looking into the version applicability. I'd bet that under the covers IDLE is relying on the traceback module too. Anyone have a Windows CPython 2.7.3 and care to check the output of the test code in a cmd window? I originally ran it unindented

[issue16855] traceback module leaves off module name in last line of formatted tracebacks

Terry J. Reedy added the comment: console = cmd window. I did run it there and that is where I duplicated your 2.7.3 result. I don't understand the different result with 2.7.3 IDLE, since it runs in a separate pythonw process that *should* give the same result as the python cmd window. But

[issue16855] traceback module leaves off module name in last line of formatted tracebacks

Terry J. Reedy added the comment: On Win7, 2.7.3 gives me the same output. (Running in IDLE, I don't get the 'socket.' prefix even on the second traceback.) With 3.3, I get socket.timeout both times (console or IDLE). So the problem seems to be 2.x only. print_exc calls print_exception, which

[issue16855] traceback module leaves off module name in last line of formatted tracebacks

New submission from Walter Mundt: The documentation for the traceback module states that it exactly mimics the behavior of the Python interpreter when it prints a stack trace. However, this does not seem to be the case. In Python 2.7.3, executing the following: import socket import