[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Fabio Zadrozny
New submission from Fabio Zadrozny fab...@users.sourceforge.net: sys.exc_clear() does not seem to exist in Python 3.0 anymore, so, a way to deal with it should be provided (maybe put a #TODO comment and point to somewhere explaining what happened?). -- components: 2to3 (2.x to 3.0

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: There should be no need for sys.exc_clear() anymore. What are you trying to achieve? -- nosy: +pitrou ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4719

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: In any case, probably a documentation issue :)) -- assignee: - georg.brandl components: +Documentation -2to3 (2.x to 3.0 conversion tool) nosy: +georg.brandl priority: - normal type: - behavior ___

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Fabio Zadrozny
Fabio Zadrozny fab...@users.sourceforge.net added the comment: When created it was already marked as a 2to3 issue (in the components), so, for clarity, yes: it's a 2to3 issue (what should the user do with that when porting... I think that the 2to3 should do something regarding that... maybe just

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: Le lundi 22 décembre 2008 à 12:48 +, Fabio Zadrozny a écrit : Fabio Zadrozny fab...@users.sourceforge.net added the comment: When created it was already marked as a 2to3 issue Oops, sorry. (because that was needed just to clear the

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Benjamin Peterson
Benjamin Peterson musiccomposit...@gmail.com added the comment: Actually, I think this should just get a Py3k warning in 2.6 and 2.7. 2to3 doesn't deal with anything else that has been removed. ___ Python tracker rep...@bugs.python.org

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Fabio Zadrozny
Fabio Zadrozny fab...@users.sourceforge.net added the comment: 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

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Benjamin Peterson
Benjamin Peterson musiccomposit...@gmail.com added the comment: In fact, there is already a Py3k warning for sys.exc_clear(). I'm still not convinced that 2to3 should play a role. What should it do? Simply remove the call? I'm apprehensive about trying to guess the intention of the user.

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Antoine Pitrou
Antoine Pitrou pit...@free.fr added the comment: If this is already handled by the -3 flag then I agree it's not a bug. ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4719 ___

[issue4719] sys.exc_clear() not flagged in any way

2008-12-22 Thread Benjamin Peterson
Changes by Benjamin Peterson musiccomposit...@gmail.com: -- resolution: - wont fix status: open - closed ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue4719 ___