There is no new syntax! It's going to remain "raise <expression1> from <expression2>". The types of the expressions are constrained by the runtime, not by the syntax. If either type is unacceptable, a TypeError (with the default context :-) will be raised. None of that is new. Really, there is no new syntax to clarify, only new allowable types for <expression2>, and a new meaning assigned to those types.
On Fri, Feb 3, 2012 at 7:28 PM, Eli Bendersky <eli...@gmail.com> wrote: > On Fri, Feb 3, 2012 at 22:14, Ethan Furman <et...@stoneleaf.us> wrote: >> Good news! PEP 409 has been accepted! >> >> Not so good news: There is no one assigned to Issue 6210 to review the >> patches... any volunteers? >> >> http://bugs.python.org/issue6210 >> > > Hi Ethan, > > I've just looked at PEP 409 online > (http://www.python.org/dev/peps/pep-0409/) and I'm not sure where it > details the final syntax that was chosen. > > The "Proposal" section says: > > " > I proprose going with the second option: > > raise NewException from None > " > > This makes no mention of ellipsis / .... > > Could you please clarify the PEP to make it detail the new syntax and > its proposed semantics more precisely? > > Thanks in advance, > Eli > _______________________________________________ > Python-Dev mailing list > Python-Dev@python.org > http://mail.python.org/mailman/listinfo/python-dev > Unsubscribe: > http://mail.python.org/mailman/options/python-dev/guido%40python.org -- --Guido van Rossum (python.org/~guido) _______________________________________________ Python-Dev mailing list Python-Dev@python.org http://mail.python.org/mailman/listinfo/python-dev Unsubscribe: http://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
