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 fabioz
Recipients benjamin.peterson, fabioz, georg.brandl, pitrou
Date 2008-12-22.13:44:52
SpamBayes Score 4.23858e-07
Marked as misclassified No
Message-id <1229953493.85.0.258889083126.issue4719@psf.upfronthosting.co.za>
In-reply-to
Content
> 2to3 doesn't deal with anything else that has been removed.

That seems a bit odd for me... isn't it the perfect place for that? (it
doesn't even need to change the code for a pass, but it could give the
user some warning about it at that specific line -- maybe with a pointer
to a place explaining why it was removed).

I think that if 2to3 flags it, it can make the porting cycle faster than
having to run the code (and expecting a huge code-coverage) to get those
-- especially as sys.exc_clear is mostly used in cases where you are
expecting some exception... and I believe not everyone gives as much
emphasis for exception cases as they'd for the cases in the 'regular flow'
History
Date User Action Args
2008-12-22 13:44:53fabiozsetrecipients: + fabioz, georg.brandl, pitrou, benjamin.peterson
2008-12-22 13:44:53fabiozsetmessageid: <1229953493.85.0.258889083126.issue4719@psf.upfronthosting.co.za>
2008-12-22 13:44:53fabiozlinkissue4719 messages
2008-12-22 13:44:52fabiozcreate