Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.python > #93493 > unrolled thread

Re: An asyncio example

Started byTerry Reedy <tjreedy@udel.edu>
First post2015-07-04 16:22 -0400
Last post2015-07-04 16:22 -0400
Articles 1 — 1 participant

Back to article view | Back to comp.lang.python

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: An asyncio example Terry Reedy <tjreedy@udel.edu> - 2015-07-04 16:22 -0400

#93493 — Re: An asyncio example

FromTerry Reedy <tjreedy@udel.edu>
Date2015-07-04 16:22 -0400
SubjectRe: An asyncio example
Message-ID<mailman.292.1436041373.3674.python-list@python.org>
On 7/4/2015 3:04 AM, Adam Bartoš wrote:

> This is a minimal example:
>
> import asyncio
>
> async def wait():
>      await asyncio.sleep(5)
>
> loop = asyncio.get_event_loop()
> loop.run_until_complete(wait())
>
> Ctrl-C doesn't interrupt the waiting, instead KeyboardInterrupt occurs
> after those five seconds. It's 3.5.0b2 on Windows. Is it a bug?

I asked on pydev list and was pointed to
https://bugs.python.org/issue23057
(where treated as missing feature ).  It is desired that this stop 
immediately on Windows as on Unix.

I suggest you post your minimal example there.  User interest in an 
issue being fixed and willingness to test patches can help motivate.

Even more minimal:

import asyncio
loop = asyncio.get_event_loop()
loop.run_forever

also not interruptible,

-- 
Terry Jan Reedy

[toc] | [standalone]


Back to top | Article view | comp.lang.python


csiph-web