On 3/21/07, Collin Winter <[EMAIL PROTECTED]> wrote: > On 3/21/07, Brett Cannon <[EMAIL PROTECTED]> wrote: > > On 3/21/07, Collin Winter <[EMAIL PROTECTED]> wrote: > > > On 3/21/07, Guido van Rossum <[EMAIL PROTECTED]> wrote: > > > > On 3/21/07, Collin Winter <[EMAIL PROTECTED]> wrote: > > > > > On 3/21/07, brett.cannon <[email protected]> wrote: > > > > > > When removing indexing/slicing on exceptions some places were > > > > > > changed > > > > > > inappropriately from ``e[0]`` to ``e.message`` instead of > > > > > > ``e.args[0]``. The > > > > > > reason it needs to be the last option is the dichotomy of 'message' > > > > > > and 'args': > > > > > > 'message' can be the empty string but args[0] can have a value if > > > > > > more than one > > > > > > argument was passed. > > > > > > > > > > So e.args is going to stick around in 3.0? > > > > > > > > I think so. e.message OTOH I think we can kill (perhaps deprecate it > > > > in 2.6; it was added in 2.5, this may be a record :-). > > > > > > I'll update 2to3's fix_except accordingly. > > > > So I guess you are just going to notice when exceptions are caught and > > if exc.message is found change it to exc.args[0]? Could you use this > > for the removal of indexing/slicing so that exc[0] becomes > > exc.args[0]? > > No, I'm basically just backing out a transformation that used .message > instead of .args. It would be possible to remove slicing/indexing like > you suggest, but only when exc is mentioned explicitly; that is, "x = > exc; x[0];" would defeat it. >
In that case I say just go with the Py3K warning thing. -Brett _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
