autobahn with uvloop policy won't work
See original GitHub issueIf uvloop event policy is set, autobahn server won’t handshake with client.
To reproduce this, just use the following:
import asyncio
import uvloop
# use uvloop loop policy
asyncio.set_event_loop_policy(uvloop.EventLoopPolicy())
Issue Analytics
- State:
- Created 6 years ago
- Comments:20 (20 by maintainers)
Top Results From Across the Web
How to use autobahn-python with existing code ? - autobahnws ...
Hi, I'm trying to play a bit with crossbar/autobahn and I'm having problems ... while True: value = await myqueue.get() <---- sounds like...
Read more >Using alternative event loop without setting global policy
It works fine, I'm just wondering whether I could run to some unexpected problems without setting the global asyncio policy to uvloop ....
Read more >I can't install python3-pip? - kali linux - Unix Stack Exchange
I'm trying to install pip3 and this happend with me ┌──(root DESKTOP-LUEK8HJ)-[/tmp] └─# apt install python3-pip Reading package lists ...
Read more >v3.7.3 PDF - aiohttp Documentation
11 Policy for Backward Incompatible Changes ... Sometimes canonicalization is not desirable if server accepts exact representation and does ...
Read more >Uvloop: Ultra Fast Asyncio Event Loop - Morioh
It has no dependencies except ones which live in the Python standard library. It runs on CPython on Unix and Windows under Python...
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 FreeTop 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
Top GitHub Comments
@meejah I’m testing
uvloop
with some Python 3 Crossbar components right now and it seems to work fine. In fact, comparing the VIRT/RES usage betweenuvloop
and the default event loop I noticed thatuvloop
seems to be vastly more resource efficientYeah, I understand. So, in fact, I don’t see anything why we couldn’t have the Crossbar.io container worker shell implemented also in an aslo flavor and make that available as a new worker subtype: twisted or asyncio. We could do that for container workers in Crossbar.io. Not for router workers. However, Crossbar.io container workers already bring the benefit you are after: ability to run, manage and monitor many components in a single process.