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 amaury.forgeotdarc
Recipients amaury.forgeotdarc, benjamin.peterson, brett.cannon, daniel.urban, georg.brandl, july, ncoghlan
Date 2011-03-08.23:37:54
SpamBayes Score 1.5424945e-05
Marked as misclassified No
Message-id <1299627474.78.0.825094461784.issue11441@psf.upfronthosting.co.za>
In-reply-to
Content
Why is the exception normalized at the end? I suppose it's because when value is an exception instance, it's replaced by a tuple, but the original value has to be recreated at the end. So in some cases, the SyntaxError object is created twice...

If PyErr_NormalizeException() can't be avoided, I suggest to call it at the start, just after PyErr_Fetch, and use the PySyntaxErrorObject* structure directly to get the file name and line numbers.
History
Date User Action Args
2011-03-08 23:37:54amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, brett.cannon, georg.brandl, ncoghlan, benjamin.peterson, july, daniel.urban
2011-03-08 23:37:54amaury.forgeotdarcsetmessageid: <1299627474.78.0.825094461784.issue11441@psf.upfronthosting.co.za>
2011-03-08 23:37:54amaury.forgeotdarclinkissue11441 messages
2011-03-08 23:37:54amaury.forgeotdarccreate