On Fri, Feb 21, 2014 at 9:32 AM, Antoine Pitrou <solip...@pitrou.net> wrote:
> On Sat, 22 Feb 2014 02:52:59 +1100 > Chris Angelico <ros...@gmail.com> wrote: > > > On Sat, Feb 22, 2014 at 1:34 AM, Brett Cannon <br...@python.org> wrote: > > > While I like the general concept, I agree that it looks too much like a > > > crunched statement; the use of the colon is a non-starter for me. I'm > sure > > > I'm not the only one whose brain has been trained to view a colon in > Python > > > to mean "statement", period. This goes against that syntactic practice > and > > > just doesn't work for me. > > > > > > I'm -1 with the current syntax, but it can go into the + range if a > better > > > syntax can be chosen. > > > > We bikeshedded that extensively on -ideas. The four best options are: > > > > value = (expr except Exception: default) > > -0.5 > > > value = (expr except Exception -> default) > > -0.5 > > > value = (expr except Exception pass default) > > -1 (looks terribly weird) > > > value = (expr except Exception then default) > > +0.5 > But I'm aware it requires reserving "then" as a keyword, which might > need a prior SyntaxWarning. > I'm put off by the ':' syntax myself (it looks to me as if someone forgot a newline somewhere) but 'then' feels even weirder (it's been hard-coded in my brain as meaning the first branch of an 'if'). I am going to sleep on this. -- --Guido van Rossum (python.org/~guido)
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
