| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | gh-103462: Ensure SelectorSocketTransport.writelines registers a writer when ↵ | Ali-Akber Saifee | 2023-04-13 | 1 | -0/+3 |
| | | | | | data is still pending (#103463) | ||||
| * | gh-102780: Fix uncancel() call in asyncio timeouts (#102815) | Kristján Valur Jónsson | 2023-03-22 | 1 | -3/+4 |
| | | | | | | | | Also use `raise TimeOut from <CancelledError instance>` so that the CancelledError is set in the `__cause__` field rather than in the `__context__` field. Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> | ||||
| * | gh-102810: Add docstrings to the public-facing methods of `asyncio.Timeout` ↵ | JosephSBoyle | 2023-03-19 | 1 | -0/+12 |
| | | | | | | | (#102811) Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> | ||||
| * | GH-102748: remove legacy support for generator based coroutines from ↵ | Kumar Aditya | 2023-03-16 | 1 | -2/+1 |
| | | | | | | `asyncio.iscoroutine` (#102749) Co-authored-by: Alex Waygood <Alex.Waygood@Gmail.com> | ||||
| * | GH-100112: avoid using iterable coroutines in asyncio internally (#100128) | Kumar Aditya | 2023-03-16 | 1 | -16/+6 |
| | | |||||
| * | gh-102560 Add docstrings to asyncio.TaskGroup (#102565) | JosephSBoyle | 2023-03-15 | 1 | -0/+18 |
| | | |||||
| * | Remove redundant `_ensure_future` in favor of `ensure_future` in `asyncio` ↵ | Kumar Aditya | 2023-03-07 | 1 | -6/+2 |
| | | | | | (#102398) | ||||
| * | gh-100226: Clarify StreamReader.read behavior (#101807) | Jan Gosmann | 2023-02-17 | 1 | -8/+9 |
| | | |||||
| * | GH-96764: rewrite `asyncio.wait_for` to use `asyncio.timeout` (#98518) | Kumar Aditya | 2023-02-16 | 1 | -48/+29 |
| | | | | Changes `asyncio.wait_for` to use `asyncio.timeout` as its underlying implementation. | ||||
| * | gh-101317: Add `ssl_shutdown_timeout` parameter for ↵ | beavailable | 2023-02-01 | 1 | -2/+4 |
| | | | | | | `asyncio.StreamWriter.start_tls` (#101335) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> | ||||
| * | gh-101143: Remove references to `TimerHandle` from ↵ | J. Nick Koston | 2023-01-21 | 1 | -6/+3 |
| | | | | | | `asyncio.base_events.BaseEventLoop._add_callback` (#101197) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> | ||||
| * | GH-100573: Fix server hang caused by os.stat() on named pipe (Windows) (#100959) | Guido van Rossum | 2023-01-13 | 1 | -0/+5 |
| | | |||||
| * | gh-100160: Restore and deprecate implicit creation of an event loop (GH-100410) | Serhiy Storchaka | 2023-01-13 | 1 | -1/+23 |
| | | | | | | | | | | | Partially revert changes made in GH-93453. asyncio.DefaultEventLoopPolicy.get_event_loop() now emits a DeprecationWarning and creates and sets a new event loop instead of raising a RuntimeError if there is no current event loop set. Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> | ||||
| * | GH-86508: skip binding to local addresses of different family in ↵ | Kumar Aditya | 2023-01-04 | 1 | -2/+8 |
| | | | | | `asyncio.open_connection` (#100615) | ||||
| * | GH-91166: Implement zero copy writes for `SelectorSocketTransport` in ↵ | Kumar Aditya | 2022-12-24 | 1 | -11/+75 |
| | | | | | | asyncio (#31871) Co-authored-by: Guido van Rossum <gvanrossum@gmail.com> | ||||
| * | gh-100344: Add C implementation for `asyncio.current_task` (#100345) | Itamar Ostricher | 2022-12-22 | 1 | -1/+4 |
| | | | | Co-authored-by: pranavtbhat | ||||
| * | GH-100133: fix `asyncio` subprocess losing `stderr` and `stdout` output ↵ | Kumar Aditya | 2022-12-21 | 1 | -3/+0 |
| | | | | | (#100154) | ||||
| * | GH-100363: Speed up `asyncio.get_running_loop` (#100364) | Kumar Aditya | 2022-12-21 | 1 | -0/+1 |
| | | |||||
| * | gh-100348: Fix ref cycle in `asyncio._SelectorSocketTransport` with ↵ | Richard Kojedzinszky | 2022-12-20 | 1 | -0/+4 |
| | | | | | `_read_ready_cb` (#100349) | ||||
| * | gh-99941: Ensure that asyncio.Protocol.data_received receives immutable ↵ | DarioDaF | 2022-12-10 | 2 | -3/+4 |
| | | | | | bytes (#100053) | ||||
| * | gh-93453: No longer create an event loop in get_event_loop() (#98440) | Serhiy Storchaka | 2022-12-06 | 4 | -23/+9 |
| | | | | | | | | | | | | | | | | asyncio.get_event_loop() now always return either running event loop or the result of get_event_loop_policy().get_event_loop() call. The latter should now raise an RuntimeError if no current event loop was set instead of creating and setting a new event loop. It affects also a number of asyncio functions and constructors which call get_event_loop() implicitly: ensure_future(), shield(), gather(), etc. DeprecationWarning is no longer emitted if there is no running event loop but the current event loop was set. Co-authored-by: Łukasz Langa <lukasz@langa.pl> | ||||
| * | GH-66285: fix forking in asyncio (#99769) | Kumar Aditya | 2022-11-27 | 1 | -0/+11 |
| | | | | Closes #66285 | ||||
| * | GH-66285: Revert "fix forking in asyncio" (#99756) | Kumar Aditya | 2022-11-24 | 1 | -9/+0 |
| | | |||||
| * | GH-79033: Fix asyncio.Server.wait_closed() (#98582) | Guido van Rossum | 2022-11-24 | 1 | -1/+1 |
| | | | | | | | | | | | | It was a no-op when used as recommended (after close()). I had to debug one test (test__sock_sendfile_native_failure) -- the cleanup sequence for the test fixture was botched. Hopefully that's not a portend of problems in user code -- this has never worked so people may well be doing this wrong. :-( Co-authored-by: kumar aditya | ||||
| * | GH-66285: fix forking in `asyncio` (#99539) | Kumar Aditya | 2022-11-24 | 1 | -0/+9 |
| | | | | `asyncio` now does not shares event loop and signal wakeupfd in forked processes. | ||||
| * | gh-88863: Clear ref cycles to resolve leak when asyncio.open_connection ↵ | Dong Uk, Kang | 2022-11-22 | 3 | -14/+35 |
| | | | | | | | | raises (#95739) Break reference cycles to resolve memory leak, by removing local exception and future instances from the frame | ||||
| * | GH-99388: add `loop_factory` parameter to `asyncio.run` (#99462) | Kumar Aditya | 2022-11-14 | 1 | -2/+2 |
| | | |||||
| * | GH-94597: add deprecation warnings for subclassing `AbstractChildWatcher` ↵ | Kumar Aditya | 2022-11-12 | 1 | -0/+7 |
| | | | | | (#99386) | ||||
| * | gh-99277: remove older version of `get_write_buffer_limits` (#99280) | Carlo | 2022-11-10 | 1 | -6/+0 |
| | | | | Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> | ||||
| * | GH-90352: fix _SelectorDatagramTransport to inherit from DatagramTransport ↵ | Kumar Aditya | 2022-10-29 | 1 | -1/+1 |
| | | | | | (#98844) | ||||
| * | gh-98703: Fix asyncio proactor_events calling _call_connection_lost multiple ↵ | Ken Jin | 2022-10-27 | 1 | -0/+2 |
| | | | | | | times (GH-98704) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> | ||||
| * | GH-89237: fix hang in proactor `subprocess.wait_closed()` (#98572) | Kumar Aditya | 2022-10-24 | 1 | -1/+3 |
| | | |||||
| * | GH-98539: fix ref cycle in `_SSLProtocolTransport` after close (#98540) | Kumar Aditya | 2022-10-22 | 1 | -2/+5 |
| | | |||||
| * | GH-98543: Fix `asyncio.TaskGroup` to not keep reference to errors after ↵ | Kumar Aditya | 2022-10-22 | 1 | -5/+5 |
| | | | | | raising ExceptionGroup (#98544) | ||||
| * | GH-98327: Reduce scope of catch_warnings() in _make_subprocess_transport ↵ | Kumar Aditya | 2022-10-17 | 1 | -24/+25 |
| | | | | | | (#98333) Alas, warnings.catch_warnings() has global scope, not thread scope, so this is still not perfect, but it reduces the time during which warnings are ignored. Better solution welcome. | ||||
| * | GH-94597: Deprecate child watcher getters and setters (#98215) | Kumar Aditya | 2022-10-15 | 1 | -24/+32 |
| | | | | | | | | This is the next step for deprecating child watchers. Until we've removed the API completely we have to use it, so this PR is mostly suppressing a lot of warnings when using the API internally. Once the child watcher API is totally removed, the two child watcher implementations we actually use and need (Pidfd and Thread) will be turned into internal helpers. | ||||
| * | Bpo-41246: IOCP Proactor avoid callback code duplication (#21399) | Tony Solomonik | 2022-10-13 | 1 | -65/+17 |
| | | | | Use the same callback function for overlapped operations recv, recv_into, recvfrom, sendto, send, and sendfile inside IocpProactor. | ||||
| * | bpo-46364: Use sockets for stdin of asyncio only on AIX (#30596) | Christoph Hamsen | 2022-10-13 | 1 | -4/+3 |
| | | | | | Signed-off-by: Christoph Hamsen <hamsen.christoph@posteo.de> Co-authored-by: July Tikhonov <july.tikh@gmail.com> | ||||
| * | GH-94597: deprecate `SafeChildWatcher`, `FastChildWatcher` and ↵ | Kumar Aditya | 2022-10-08 | 1 | -0/+15 |
| | | | | | `MultiLoopChildWatcher` child watchers (#98089) | ||||
| * | GH-98023: Change default child watcher to PidfdChildWatcher on supported ↵ | Kumar Aditya | 2022-10-08 | 1 | -1/+15 |
| | | | | | systems (#98024) | ||||
| * | GH-94182: Run the PidfdChildWatcher on the running loop (#94184) | Thomas Grainger | 2022-10-08 | 1 | -32/+12 |
| | | | | | | | | | There is no reason for this watcher to be attached to any particular loop. This should make it safe to use regardless of the lifetime of the event loop running in the main thread (relative to other loops). Co-authored-by: Yury Selivanov <yury@edgedb.com> Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com> | ||||
| * | GH-88968: Reject socket that is already used as a transport (#98010) | Guido van Rossum | 2022-10-07 | 1 | -0/+3 |
| | | |||||
| * | GH-90985: Revert "Deprecate passing a message into cancel()" (#97999) | Guido van Rossum | 2022-10-07 | 2 | -11/+0 |
| | | | | | | Reason: we were too hasty in deprecating this. We shouldn't deprecate it before we have a replacement. | ||||
| * | GH-88050: fix race in closing subprocess pipe in asyncio (#97951) | Kumar Aditya | 2022-10-06 | 1 | -1/+3 |
| | | | | Check for None when iterating over `self._pipes.values()`. | ||||
| * | gh-88050: Fix asyncio subprocess to kill process cleanly when process is ↵ | Kumar Aditya | 2022-10-05 | 1 | -6/+7 |
| | | | | | blocked (#32073) | ||||
| * | GH-96704: Add {Task,Handle}.get_context(), use it in ↵ | Guido van Rossum | 2022-10-05 | 3 | -1/+22 |
| | | | | | | call_exception_handler() (#96756) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com> | ||||
| * | gh-94732: Fix KeyboardInterrupt race in asyncio run_forever() (#97765) | hetmankp | 2022-10-03 | 1 | -3/+4 |
| | | | | Ensure that the event loop's `_thread_id` attribute and the asyncgen hooks set by `sys.set_asyncgen_hooks()` are always restored no matter where a KeyboardInterrupt exception is raised. | ||||
| * | gh-90908: Document asyncio.Task.cancelling() and asyncio.Task.uncancel() ↵ | Łukasz Langa | 2022-10-01 | 1 | -2/+2 |
| | | | | | | | (#95253) Co-authored-by: Thomas Grainger <tagrain@gmail.com> | ||||
| * | GH-96827: Don't touch closed loops from executor threads (#96837) | Guido van Rossum | 2022-09-30 | 2 | -2/+6 |
| | | | | | | * When chaining futures, skip callback if loop closed. * When shutting down an executor, don't wake a closed loop. | ||||
| * | GH-82448: Add thread timeout for loop.shutdown_default_executor (#97561) | Kumar Aditya | 2022-09-28 | 3 | -7/+26 |
| | | | | | Co-authored-by: Kyle Stanley <aeros167@gmail.com> | ||||
