ACTIVITY SUMMARY (2018-06-08 - 2018-06-15)
Python tracker at https://bugs.python.org/
To view or respond to any of the issues listed below, click on the issue.
Do NOT respond to this message.
Issues counts and deltas:
open6691 ( -1)
closed 38930 (+62)
total 45621 (+61)
Open issues wi
On Fri, 15 Jun 2018 at 09:18, Michel Desmoulin
wrote:
>
> >
> > The strict API compatibility requirements of core Python stdlib, coupled
> > with the very long feature release life-cycles of Python, make me think
> > this sort of thing perhaps is better built in an utility library on top
> > of a
On 14 June 2018 at 06:30, Ronald Oussoren wrote:
> On 13 Jun 2018, at 15:42, Nick Coghlan wrote:
>
> Yeah, pretty much - once we can get to the point where it's routine for
> folks to be building "abiX" or "abiXY" wheels (with the latter not actually
> being a defined compatibility tag yet, but
Le 14/06/2018 à 04:09, Nathaniel Smith a écrit :
> How about:
>
> async def wait_to_run(async_fn, *args):
> await wait_for_something()
> return await async_fn(*args)
>
> task = loop.create_task(wait_to_run(myfunc, ...))
>
It's quite elegant, although figuring out the wait_for_somethin
>
> The strict API compatibility requirements of core Python stdlib, coupled
> with the very long feature release life-cycles of Python, make me think
> this sort of thing perhaps is better built in an utility library on top
> of asyncio, rather than inside asyncio itself? 18 months is a long lo
On Thu, Jun 14, 2018 at 8:14 PM, Chris Barker via Python-Dev <
python-dev@python.org> wrote:
> Excuse my ignorance (or maybe it's a vocabulary thing), but I'm trying to
> understand the problem here.
>
> So why do queries fail with 1 tasks? or ANY number? If the async DB
> access code is wri
