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: asyncio - run coroutine in the background
Date: Sun, 14 Feb 2016 23:39:07 -0800
Organization: A noiseless patient Spider
Lines: 13
Message-ID: <87h9ha8lt0.fsf@jester.gateway.pace.com>
References: <mailman.131.1455518141.22075.python-list@python.org> <8737sumpjl.fsf@elektro.pacujo.net> <mailman.132.1455520607.22075.python-list@python.org>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="89fc4f87faf042e7e4d428a3639a51e3"; logging-data="4970"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX18YkaM1HlskP3pkk+4p/6hA"
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (gnu/linux)
Cancel-Lock: sha1:0xSMwrOAhpzURhk6yosbctMotGE= sha1:nJDagVmFhLcZ9VBvPWfkdioqRoA=
Xref: csiph.com comp.lang.python:102946

"Frank Millman" <frank@chagford.com> writes:
> The benefit of my class is that it enables me to take the coroutine
> and run it in another thread, without having to re-engineer the whole
> thing.

Threads in Python don't get you parallelism either, of course.

I haven't used async/await yet and it's looking painful.  I've been
wanting to read this:

 http://www.snarky.ca/how-the-heck-does-async-await-work-in-python-3-5

but I start to think it isn't all that great an approach to concurrency.