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 Mathias Fröjdman, gvanrossum, martin.panter, vstinner, yselivanov
Date 2015-08-06.09:10:42
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <CAP7+vJK1Jf3j=4VnwBtuws3z7-rF=vE9XUD2Ph+c8_EyUNw8dw@mail.gmail.com>
In-reply-to <1438822673.0.0.0953982247495.issue24795@psf.upfronthosting.co.za>
Content
My worry is that the context manager will make people believe it's a good
pattern to create an event loop just to make one call. If tests violate
this pattern, add a context manager helper function to test_utils.py.

On Thu, Aug 6, 2015 at 2:57 AM, Martin Panter <report@bugs.python.org>
wrote:

>
> Martin Panter added the comment:
>
> >From what I can see, the examples in the current documentation tend to
> diectly call loop.close() without an exception handler. Only two examples
> have the bare-bones try / finally handler (which is important for the
> example that uses Ctrl+C).
>
> ----------
> nosy: +vadmium
>
> _______________________________________
> Python tracker <report@bugs.python.org>
> <http://bugs.python.org/issue24795>
> _______________________________________
>
History
Date User Action Args
2015-08-06 09:10:43gvanrossumsetrecipients: + gvanrossum, vstinner, martin.panter, yselivanov, Mathias Fröjdman
2015-08-06 09:10:42gvanrossumlinkissue24795 messages
2015-08-06 09:10:42gvanrossumcreate