I think it could even be true without, but the colon may cause ambiguity problems with function annotations. 

   def foo(delayed: delayed: 1 + 2)

is a bit odd, especially if `delayed` is chainable.

--Josh

On Fri, Feb 17, 2017 at 3:32 PM Joseph Hackman <josephhackman@gmail.com> wrote:

Couldn't the same thing be true of delayed if it is always followed by a colon?

I.e. 

delayed=1

x= delayed: slow_function()

print(delayed) # prints 1

-Joseph

On Feb 17, 2017, at 2:39 PM, Mark E. Haase <mehaase@gmail.com> wrote:

On Fri, Feb 17, 2017 at 1:55 PM, Joshua Morton <joshua.morton13@gmail.com> wrote:

but I'm wondering how common async and await were when that was proposed and accepted?

Actually, "async" and "await" are backwards compatible due to a clever tokenizer hack. The "async" keyword may only appear in a few places (e.g. async def), and it is treated as a name anywhere else.The "await" keyword may only appear inside an "async def" and is treated as a name everywhere else. Therefore...

    >>> async = 1

    >>> await = 1

...these are both valid in Python 3.5. This example is helpful when proposing new keywords.

More info: https://www.python.org/dev/peps/pep-0492/#transition-plan

_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/

_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/

_______________________________________________
Python-ideas mailing list
Python-ideas@python.org
https://mail.python.org/mailman/listinfo/python-ideas
Code of Conduct: http://python.org/psf/codeofconduct/