multiple async web frameworks in venv breaks aiohttp Server run #745
Replies: 2 comments
-
|
I can't reproduce this. I have a venv with all the frameworks installed, and aiohttp does not appear to have a collision with eventlet. I can run the aiohttp server example in this repo with and without the async_mode option set and both work fine. The error that you have could indicate that you have monkey patched the standard library for eventlet, which will definitely prevent any asyncio app from running. |
Beta Was this translation helpful? Give feedback.
-
|
@FifthHour I definitely welcome all reports of possible bugs. This problem you are seeing is definitely something that I wouldn't want to ignore, but given that I cannot reproduce it myself, maybe it would be a good idea if you can come up with a simple example that shows this problem. If you show me the code, the version of Python and the output of |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
Thank you for this amazing library.
Just a wee heads up I spotted a small issue.
Initially, I was running my socketio.AsyncServer perfectly fine like so:
then, in the same venv, for another thing (i was just experimenting) I pip installed
eventlet.With no changes to the above code at all, i then got the error posted at the end. My server wouldn not run.
After some head scratching, I tried installing eventlet, and the error went away.
Conscious having two async web frameworks in one venv may be bad practice, however the param
async_mode='aiohttp'i guess implies you can force one to be selected.It just surprised me that even having eventlet in my venv caused this error.
Many thanks
Beta Was this translation helpful? Give feedback.
All reactions