We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
The asyncio ConnectionPool contains a lot of code, inherited from the synchronous part, which tries to play safe with sockets after a fork() call.
ConnectionPool
fork()
However, python asyncio and fork does not play well together at all: python/cpython#66197
Basically, one should never fork a process with a running event loop. As such, the code comparing PIDs is not helping with anything for async.
I propose that these rudiments be removed from the async code for clarity and simplicity.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
The asyncio
ConnectionPool
contains a lot of code, inherited from the synchronous part, which tries to play safe with sockets after afork()
call.However, python asyncio and fork does not play well together at all:
python/cpython#66197
Basically, one should never fork a process with a running event loop. As such, the code comparing PIDs is not helping with anything for async.
I propose that these rudiments be removed from the async code for clarity and simplicity.
The text was updated successfully, but these errors were encountered: