[issue7378] unexpected truncation of traceback

Serhiy Storchaka added the comment: 3.1 gets only security fixes. In 2.7 and 3.2+ the bug has already fixed. -- nosy: +serhiy.storchaka resolution: -> out of date stage: patch review -> committed/rejected status: open -> closed ___ Python tracker

[issue7378] unexpected truncation of traceback

Changes by Ezio Melotti : -- nosy: +ezio.melotti versions: +Python 3.2 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubsc

[issue7378] unexpected truncation of traceback

Daniel Diniz added the comment: Patch still applies to py3k, not applying cleanly to trunk anymore. Tests pass with patch on py3k. -- nosy: +ajaksu2 priority: -> normal stage: -> patch review ___ Python tracker

[issue7378] unexpected truncation of traceback

New submission from Greg Hewgill : Quite by accident, I came across a case where Python would quit generating traceback text and skip printing the actual exception information. Here is a sample program: exec(compile("spam()", ".", "exec")) and the output in Python 3.1 ("spam" is undefined):