Re: Using asyncio workers in a `concurrent.futures` interface

Path	csiph.com!v102.xanadu-bbs.net!xanadu-bbs.net!feeder.erje.net!eu.feeder.erje.net!newsfeed.xs4all.nl!newsfeed2a.news.xs4all.nl!xs4all!post.news.xs4all.nl!not-for-mail
Return-Path	<ian.g.kelly@gmail.com>
X-Original-To	python-list@python.org
Delivered-To	python-list@mail.python.org
X-Spam-Status	OK 0.036
X-Spam-Evidence	'H': 0.93; 'S': 0.00; 'feasible.': 0.09; 'subject:skip:c 10': 0.09; 'thread': 0.14; 'executor': 0.16; 'wrote:': 0.18; 'aug': 0.22; 'putting': 0.22; 'separate': 0.22; 'header:In-Reply-To:1': 0.27; 'am,': 0.29; 'message- id:@mail.gmail.com': 0.30; "i'm": 0.30; 'run': 0.32; 'sense': 0.34; 'could': 0.34; 'but': 0.35; 'received:google.com': 0.35; 'done,': 0.36; 'to:addr:python-list': 0.38; '12,': 0.39; 'to:addr:python.org': 0.39; 'subject:Using': 0.84
DKIM-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=/uPXvcXb9yK25sLRMKoKvxOu89smmonL0WN9XAFgceA=; b=hSgx/uG6SPsjBgogvLxL5XevH5SCKhE678n8yfQG08eQ/79ZGr1OJCLN0bUOvsM1K3 2EceM3Lp4HIukvQlYR/u0R2+5s9LSBlCfTkeqQP8oEGpVHGy9p3I42EbGOTpGOLsU795 LMVx95tnx04+g9D8PjU32jYcqfBIz7Pj21bhGSyVbQAt9JZHdrcx2nYs4E9yERaBflOw Qp+ATnsDLgD9naNigvHhIz19e2NBGqaj5KgszKkA7tsChWbPrzfATFNI+ncq6vUdG+/l EXZHwWnLIrJmfq+iNdQnge6vpfK0WVLKFrwfVKHZQVpY5td6AaoUkyjWVNkqigRnJS2o c8Cw==
X-Received	by 10.68.68.131 with SMTP id w3mr357318pbt.90.1407879135791; Tue, 12 Aug 2014 14:32:15 -0700 (PDT)
MIME-Version	1.0
In-Reply-To	<d6e2ab63-c9bc-4271-abac-17e32afa4c88@googlegroups.com>
References	<d6e2ab63-c9bc-4271-abac-17e32afa4c88@googlegroups.com>
From	Ian Kelly <ian.g.kelly@gmail.com>
Date	Tue, 12 Aug 2014 15:31:35 -0600
Subject	Re: Using asyncio workers in a `concurrent.futures` interface
To	Python <python-list@python.org>
Content-Type	text/plain; charset=UTF-8
X-BeenThere	python-list@python.org
X-Mailman-Version	2.1.15
Precedence	list
List-Id	General discussion list for the Python programming language <python-list.python.org>
List-Unsubscribe	<https://mail.python.org/mailman/options/python-list>, <mailto:python-list-request@python.org?subject=unsubscribe>
List-Archive	<http://mail.python.org/pipermail/python-list/>
List-Post	<mailto:python-list@python.org>
List-Help	<mailto:python-list-request@python.org?subject=help>
List-Subscribe	<https://mail.python.org/mailman/listinfo/python-list>, <mailto:python-list-request@python.org?subject=subscribe>
Newsgroups	comp.lang.python
Message-ID	<mailman.12901.1407879145.18130.python-list@python.org> (permalink)
Lines	7
NNTP-Posting-Host	2001:888:2000:d::a6
X-Trace	1407879145 news.xs4all.nl 2951 [2001:888:2000:d::a6]:40806
X-Complaints-To	abuse@xs4all.nl
Xref	csiph.com comp.lang.python:76152

Show key headers only | View raw

On Tue, Aug 12, 2014 at 11:02 AM, cool-RR <ram.rachum@gmail.com> wrote:
> And that's it, no coroutines, no `yield from`. Since, if I understand correctly, asyncio requires a mainloop, it would make sense for the AsyncIOExecutor to have a thread of its own in which it could run its mainloop.

I think that putting the event loop in a separate thread would be
necessary if the intention is that the executor be invoked from
outside. I'm not aware of this work having been done, but it sounds
perfectly feasible.

Thread

Using asyncio workers in a `concurrent.futures` interface cool-RR <ram.rachum@gmail.com> - 2014-08-12 10:02 -0700
  Re: Using asyncio workers in a `concurrent.futures` interface Marko Rauhamaa <marko@pacujo.net> - 2014-08-12 21:31 +0300
  Re: Using asyncio workers in a `concurrent.futures` interface MRAB <python@mrabarnett.plus.com> - 2014-08-12 19:43 +0100
  Re: Using asyncio workers in a `concurrent.futures` interface Ian Kelly <ian.g.kelly@gmail.com> - 2014-08-12 15:31 -0600
    Re: Using asyncio workers in a `concurrent.futures` interface Marko Rauhamaa <marko@pacujo.net> - 2014-08-13 08:03 +0300
      Re: Using asyncio workers in a `concurrent.futures` interface Ian Kelly <ian.g.kelly@gmail.com> - 2014-08-13 00:03 -0600

csiph-web