Dag Sverre Seljebotn, 13.03.2010 10:51: > Stefan Behnel wrote: >> Robert Bradshaw, 13.03.2010 09:25: >>>> >>> e = None >>>> >>> try: raise ValueError >>>> ... except ValueError as e: pass >>>> ... >>>> >>> e >>> In the face of differing behavior Cython follows Python 2.x scoping >>> conventions, e.g. the same issue arises for list comprehensions. >> >> It's actually very easy for the exception case. You could have Py2 scoping >> for >> >> except ValueError, e: >> >> and Py3 scoping for >> >> except ValueError as e: > > -1 from me on that one -- way too obscure.
I can't really share your concern here. We are talking about two different spellings that are well defined as having different semantics. If you know about the second, you'll expect Py3 semantics when you use it. If you use the first, you'll expect Py2 semantics. For both, you likely won't care about the difference in most cases. Anyway, I could certainly live with Py3 semantics for both. :) Stefan _______________________________________________ Cython-dev mailing list [email protected] http://codespeak.net/mailman/listinfo/cython-dev
