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.

Author gvanrossum
Recipients asvetlov, gvanrossum, martin.panter, ncoghlan, vstinner, yselivanov
Date 2015-12-16.23:53:31
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJLuy4k6v0=R6vhi1hXBcuV3e6W7JcE2KD_FBc55MzNFxw@mail.gmail.com>
In-reply-to <1450309727.07.0.0131171716489.issue25887@psf.upfronthosting.co.za>
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>
> _______________________________________
>
History
Date User Action Args
2015-12-16 23:53:31gvanrossumsetrecipients: + gvanrossum, ncoghlan, vstinner, asvetlov, martin.panter, yselivanov
2015-12-16 23:53:31gvanrossumlinkissue25887 messages
2015-12-16 23:53:31gvanrossumcreate