➜

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-09.09:44:11
SpamBayes Score 0.00042485734
Marked as misclassified No
Message-id <1299663851.91.0.671679513551.issue11441@psf.upfronthosting.co.za>
In-reply-to
Content 
> That's why I thought that calling PyErr_NormalizeException with the new
> tuple is the simplest thing to do, becuase I guess that'll take care of
> all fields automatically.

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.
History
Date User Action Args
2011-03-09 09:44:11amaury.forgeotdarcsetrecipients: + amaury.forgeotdarc, brett.cannon, georg.brandl, ncoghlan, benjamin.peterson, july, daniel.urban
2011-03-09 09:44:11amaury.forgeotdarcsetmessageid: <1299663851.91.0.671679513551.issue11441@psf.upfronthosting.co.za>
2011-03-09 09:44:11amaury.forgeotdarclinkissue11441 messages
2011-03-09 09:44:11amaury.forgeotdarccreate