On 28 February 2014 23:07, Chris Angelico <[email protected]> wrote: > On Fri, Feb 28, 2014 at 11:51 PM, Nick Coghlan <[email protected]> wrote: >> So I think that on balance, I actually do prefer your current >> proposal. That said, I do think this is a variant worth discussing >> explicitly in the PEP, if only to remind people that there's >> definitely precedent for using a colon to separate two subexpressions >> inside a larger expression element - it's not *just* used to introduce >> suites, even though that is by far the most *common* use case. > > I've added a bit more to the PEP about that. > > https://github.com/Rosuav/ExceptExpr/commit/f32387 > > Does that explain it, do you think?
Yeah, that works. You may also want to add a "common objections" section to explicitly cover the "but colons introduce suites" objection. That would provide a space to explicitly list all of the current "not introducing a suite" use cases for the colon in Python's syntax, since increasing that tally from four to five is less radical than introducing the first non-suite related use case for the symbol. Cheers, Nick. -- Nick Coghlan | [email protected] | Brisbane, Australia _______________________________________________ Python-Dev mailing list [email protected] https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com