[issue27598] Add SizedIterable to collections.abc and typing

Sven R. Kunze added the comment: I am way too late to the discussion but I also support the term "collections". I think it also helps developers coming from a C# background: https://msdn.microsoft.com/library/92t2ye13(v=vs.110).aspx -- nosy

[issue24578] [RFE] Add asyncio.wait_for_result API

New submission from Sven R. Kunze: In order to complement http://bugs.python.org/issue24571, this is another high-level convenience API for asyncio to treat an awaitable like a usual subroutine (credits go to Nick Coghlan): # Call awaitable from synchronous code def wait_for_result

[issue24578] [RFE] Add asyncio.wait_for_result API

Changes by Sven R. Kunze : -- nosy: +giampaolo.rodola, ncoghlan, pitrou -srkunze type: -> enhancement ___ Python tracker <http://bugs.python.org/issu

[issue24578] [RFE] Add asyncio.wait_for_result API

Changes by Sven R. Kunze : -- nosy: +srkunze ___ Python tracker <http://bugs.python.org/issue24578> ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue24571] [RFE] Add asyncio.blocking_call API

Sven R. Kunze added the comment: Thanks for taking the initiative here, Nick. I created a follow-up on this: http://bugs.python.org/issue24578 In order to bridge both worlds, projects might need convenient way from and to either world (classic and asyncio). -- components: +asyncio

[issue24571] [RFE] Add asyncio.blocking_call API

Sven R. Kunze added the comment: 2 remarks: 1) I would rather go for a more comprehensible name such as 'get_awaitable' instead of 'blocking_call'. Later reminds me of the execution of f which is not the case. 2) redundant ) in the end of """Usage: res

[issue24571] [RFE] Add asyncio.call_async API

Sven R. Kunze added the comment: > Why bother with asyncio at all? Good question. My initial reaction to async+await was: 'great, finally a Pythonic (i.e. a single, explicit) way to do squeeze out more of our servers'. Moreover, the goal of 'being more like classic code

[issue24571] [RFE] Add asyncio.call_async API

Sven R. Kunze added the comment: > I also fear adding too many functions to do the same things. > > For example, scheduling the execution of a coroutine can now be done by: > * asyncio.async(coro) > * asyncio.Task(coro) > * loop.create_task(coro) > * asyncio.ensure_task

[issue24571] [RFE] Add asyncio.call_async API

Sven R. Kunze added the comment: @David What is the purpose of multitasking code? -- ___ Python tracker <http://bugs.python.org/issue24571> ___ ___ Python-bug

[issue24571] [RFE] Add asyncio.background_call API

Sven R. Kunze added the comment: > ... this sounds like it is encouraging staying ignorant. True. However, I being ignorant about the complexity eventually led to the development of high-level languages like Python. Each time, a next generation simply asks the question: 'does it rea