asyncio
asyncio copied to clipboard
asyncio historical repository
The problem is: `writer.close()` is a regular method which calls `transport.close()`. But `transport.close()` actually closes the connection only on next loop iteration by `self._loop.call_soon(self._call_connection_lost, None)` call`. Now a safe way...
This is a continuation of issue #464 Remove import asyncio.test_utils completely. This is an internal module, and has nothing to do with examples (which historically were just experiments with asyncio,...
Changed all the import statements in all modules in the examples directory to import only what is needed. This fixes issue #464
Dear all, Following the bug #414, here is a patch which makes the fork + exec operation non blocking on Unix. The patch is probably not ready to land, but...
#### Target Python 3.6b3 #### Background In Python 3.6, `socket.close()` method will propagate any `OSError` from the underlying syscall (see [issue #26685](http://bugs.python.org/issue26685) for details.) What it means for alternative implementations...
I think I've figured out what's going on with `remove_signal_handler`. This PR fixes: * https://github.com/python/asyncio/issues/396 * http://bugs.python.org/issue23548 * http://bugs.python.org/issue28628
does this adapt to pep8? I was told not to write code in this way. this will add more work to the people who want to use your work, we...
I recently discovered that Linux/OS X provide an important API (TCP_NOTSENT_LOWAT) that lets applications avoid queuing up excessive data inside the kernel's socket send buffers. (The socket send buffers are...
asyncio.wait has 3 different options to run with Constant Description FIRST_COMPLETED The function will return when any future finishes or is cancelled. FIRST_EXCEPTION The function will return when any future...