Re: Question about asyncio and blocking operations

From	Paul Rubin <no.email@nospam.invalid>
Newsgroups	comp.lang.python
Subject	Re: Question about asyncio and blocking operations
Date	2016-01-25 23:53 -0800
Organization	A noiseless patient Spider
Message-ID	<87io2gsro8.fsf@jester.gateway.pace.com> (permalink)
References	(2 earlier) <n84obi$o5d$1@ger.gmane.org> <CALwzidkUqejrB_UqEK5ero8FkEh7rOwXS=6McbdX9E1QKiocdw@mail.gmail.com> <mailman.219.1453736755.15297.python-list@python.org> <ea0ee208-7ba0-469a-98fb-8eb030b16bee@googlegroups.com> <87si1ku7lq.fsf@elektro.pacujo.net>

Show all headers | View raw

Marko Rauhamaa <marko@pacujo.net> writes:
> Note that neither the multithreading model (which I dislike) nor the
> callback hell (which I like) suffer from this problem.

There are some runtimes (GHC and Erlang) where everything is nonblocking
under the covers, which lets even the asyncs be swept under the rug.
Similarly with some low-tech cooperative multitaskers, say in Forth.
When you've got a mixture of blocking and nonblocking, it becomes a
mess.

Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Re: Question about asyncio and blocking operations Ian Kelly <ian.g.kelly@gmail.com> - 2016-01-25 08:45 -0700
  Re: Question about asyncio and blocking operations Rustom Mody <rustompmody@gmail.com> - 2016-01-25 22:01 -0800
    Re: Question about asyncio and blocking operations Marko Rauhamaa <marko@pacujo.net> - 2016-01-26 09:23 +0200
      Re: Question about asyncio and blocking operations Paul Rubin <no.email@nospam.invalid> - 2016-01-25 23:53 -0800

csiph-web