Message 256568 - Python tracker

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Content
PEP 492 is provisional, we can change things like this in 3.5.2.

On Wed, Dec 16, 2015 at 3:48 PM, Martin Panter <report@bugs.python.org>
wrote:

>
> Martin Panter added the comment:
>
> It should always be valid to create a new coroutine instance. Perhaps you
> meant:
>
> instance = foo()
> print(await instance)  # Okay the first time
> print(await instance)  # Second time should be an error
>
> This seems sensible, at least for 3.6. Maybe it should also be an error to
> re-await if the coroutine raised an exception, and if it was cancelled via
> close().
>
> ----------
> nosy: +martin.panter
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue25887>
> _______________________________________
>