This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author daniel.urban
Recipients amaury.forgeotdarc, benjamin.peterson, brett.cannon, daniel.urban, georg.brandl, july, ncoghlan
Date 2011-03-09.12:50:04
SpamBayes Score 2.1302856e-08
Marked as misclassified No
Message-id <1299675005.58.0.946969198242.issue11441@psf.upfronthosting.co.za>
In-reply-to
Content
> You could also call PyErr_NormalizeException at the beginning, and
> update the fields directly in the PySyntaxErrorObject structure.  No
> need to deal with any tuple.

Sorry, but I don't really understand.  If I call PyErr_NormalizeException at the beginning, the SyntaxError instance will be initialized with the wrong 3-tuple: (errstr, lineno, offset).  If after that I update the msg, filename, ... fields, they will be correct, but I think the args field still will be the wrong 3-tuple.  So I'll have to still create the new tuple, and replace the args field, right?
History
Date User Action Args
2011-03-09 12:50:05daniel.urbansetrecipients: + daniel.urban, brett.cannon, georg.brandl, amaury.forgeotdarc, ncoghlan, benjamin.peterson, july
2011-03-09 12:50:05daniel.urbansetmessageid: <1299675005.58.0.946969198242.issue11441@psf.upfronthosting.co.za>
2011-03-09 12:50:05daniel.urbanlinkissue11441 messages
2011-03-09 12:50:04daniel.urbancreate