Path: csiph.com!eternal-september.org!feeder.eternal-september.org!mx02.eternal-september.org!.POSTED!not-for-mail
From: Paul Rubin <no.email@nospam.invalid>
Newsgroups: comp.lang.python
Subject: Re: Question about asyncio and blocking operations
Date: Mon, 25 Jan 2016 23:53:11 -0800
Organization: A noiseless patient Spider
Lines: 9
Message-ID: <87io2gsro8.fsf@jester.gateway.pace.com>
References: <n8038j$575$1@ger.gmane.org> <CALwzidnGOgpx+CpMVBA8vpEFuq4-BwMVS0gZ3ShB0oWZi0Bw+Q@mail.gmail.com> <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>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="89fc4f87faf042e7e4d428a3639a51e3"; logging-data="18885"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18JfN15JF/o7ia99oszUu9Z"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:OK3tJV1NwCihdhjjROvUDfou8ys= sha1:iPiiI8YavcplOqgCFUq/7uKNGGw=
Xref: csiph.com comp.lang.python:102107

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.