asyncio coroutines support
See original GitHub issueHey, I’m wondering if I there is any plan to support exposing async coroutines? so that I can do something like this:
@expose
class Thingy(object):
async def message(self, arg):
print("Message received:", arg)
return "Roger!"
I think it would fit nicely with Pyro5 being Python 3.5+ and all.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:6
- Comments:12 (5 by maintainers)
Top Results From Across the Web
Coroutines and Tasks — Python 3.11.1 documentation
This section outlines high-level asyncio APIs to work with coroutines and Tasks. Coroutines, Awaitables, Creating Tasks, Task Cancellation, Task Groups, ...
Read more >Async IO in Python: A Complete Walkthrough
Async IO is a concurrent programming design that has received dedicated support in Python, evolving rapidly from Python 3.4 through 3.7, and probably...
Read more >Python Asyncio: The Complete Guide
The “asyncio” module provides functions and objects for developing coroutine-based programs using the asynchronous programming paradigm.
Read more >Coroutines and asyncio - IBM Developer
Python has several types of coroutines, but the focus of this tutorial is the type that's designed to support asynchronous programming.
Read more >Running coroutines in Python with Asyncio | by Cassius
At the heart of asyncio are coroutines. Coroutines are declared with the async and await syntax. They are in essence awaitable functions.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thank you for the insight!
Gevent won’t magically turn a synchronous program into an asynch system.
I’m closing this issue - I won’t be changing Pyro5 internally myself to support this. I could see a PR with a new additional socketserver implementation based on an async event loop mechanism, but I’m not going to write that myself in the forseeable future