homepage

Using sys.exc_{type,values,traceback} should raise a Py3K warning.

A fixer to use sys.exc_info is needed.

Attaching a helper patch that allows an empty ArgList in lib2to3/fixes/
util.py, which is required by my next patch.

Attaching a patch that provides fixers for sys.exc_
{type,value,traceback}

Fixer patch works for me (both must be applied).
A 3k warning for accessing is harder - it would have to copy the module
type or dict type and supply a custom to_getattro that watches for
accesses to exc_(type|values|traceback). I'll look into it.

I'd say that since this is so easy for a fixer to spot and fix, no
convoluted effort to add a Py3k warning is necessary. (The same goes
for sys.exitfunc, #2356).

I agree with Georg; a 2to3 fixer is enough.

+1, I'll burn my _apply_evil(ModuleObject *) function patch to
moduleobject.c which did a memcpy on a type object and several other
heresies.
On Tue, Mar 25, 2008 at 4:27 AM, Brett Cannon <report@bugs.python.org> wrote:
>
> Brett Cannon <brett@python.org> added the comment:
>
> I agree with Georg; a 2to3 fixer is enough.
>
>
>
> __________________________________
> Tracker <report@bugs.python.org>
> <http://bugs.python.org/issue2357>
> __________________________________
>

Collin, can you review the 2to3 patch?

Thanks for the work, Jeff! I reviewed the fixer, changed a few things,
added a few more tests, and committed it in r65968.