[ python-Bugs-1326077 ] traceback.py formats SyntaxError differently

SourceForge.net noreply at sourceforge.net
Thu Oct 13 20:28:53 CEST 2005


Bugs item #1326077, was opened at 2005-10-13 18:28
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1326077&group_id=5470

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Python Library
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Neil Schemenauer (nascheme)
Assigned to: Nobody/Anonymous (nobody)
Summary: traceback.py formats SyntaxError differently

Initial Comment:
I ran into this bug while working on the AST compiler.
 The new compiler sets the "lineno" and "filename"
attributes of SyntaxErrors in more cases than the old.
 The problem is that the traceback.py module formats
SyntaxError exceptions differently than pythonrun.c
does.  Attached is a small testcase.  Notice that
traceback.py uses str() to generate the exception line
and that it includes the file and lineno in
parenthesis.  This difference confuses doctest.py.

I guess the parse_syntax_error() logic needs to be
reproduced in traceback.py.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=105470&aid=1326077&group_id=5470


More information about the Python-bugs-list mailing list