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-10.17:57:44
SpamBayes Score 2.5517506e-06
Marked as misclassified No
Message-id <1299779866.62.0.0276704085144.issue11441@psf.upfronthosting.co.za>
In-reply-to
Content
Err... sorry, I don't understand again:

If we get a tuple, create a new, store it without normalization. That's okay, I understand.

If we get a SyntaxError instance, then take its args field, create the new tuple. Then call PyErr_NormalizeException(), with:
a) the new tuple? But this will create a new SyntaxError instance...
b) the old SyntaxError instance? But this won't correct the wrong fields of the instance. (I think SyntaxError.__init__ would correct them without creating a new instance.)
c) or replace the args of the SyntaxError instance with the new tuple, then call PyErr_NormalizeException() on the instance? But I think that still won't correct the other fields of the instance...

Sorry for all these questions... I'd just like to help.
History
Date User Action Args
2011-03-10 17:57:46daniel.urbansetrecipients: + daniel.urban, brett.cannon, georg.brandl, amaury.forgeotdarc, ncoghlan, benjamin.peterson, july
2011-03-10 17:57:46daniel.urbansetmessageid: <1299779866.62.0.0276704085144.issue11441@psf.upfronthosting.co.za>
2011-03-10 17:57:44daniel.urbanlinkissue11441 messages
2011-03-10 17:57:44daniel.urbancreate