fd6a602d04
[3.13] gh-133745: Fix asyncio task factory name/context kwarg breaks ( #133948 )
...
In 3.13.3 we accidentally broke the interface for custom task factory. Factory authors added workarounds.
This PR (for 3.13.4) unbreaks task factories that haven't made a workaround yet while also supporting those that have.
NOTE: The custom task factory API will change to what we accidentally released in 3.13.3.
Co-authored-by: Kumar Aditya <kumaraditya@python.org>
Co-authored-by: Guido van Rossum <gvanrossum@gmail.com>
2025-05-18 06:50:07 -07:00
fd0bba67c4
[3.13] gh-86513: improve docs of loop.call_exception_handler (GH-132466) ( #132487 )
...
gh-86513: improve docs of loop.call_exception_handler (GH-132466)
(cherry picked from commit ce753517a8
2025-04-14 11:42:45 +00:00
c68a8722be
[3.13] gh-121970: Replace `.. coroutine{method,function}` with `:async:` (GH-130448) ( #130465 )
...
(cherry picked from commit 5ec4bf86b7
2025-02-22 18:00:49 +00:00
7b0543ebe6
[3.13] gh-128308: pass `**kwargs` to asyncio task_factory (GH-128768) ( #130084 )
...
* [3.13] gh-128308: pass `**kwargs` to asyncio task_factory (GH-128768)
(cherry picked from commit 38a9956876
2025-02-14 22:04:17 +05:30
1d2d62c15e
[3.13] gh-126137: improve docs for `loop.add_reader` and `loop.add_writer` (GH-128666) ( #128667 )
...
gh-126137: improve docs for `loop.add_reader` and `loop.add_writer` (GH-128666)
(cherry picked from commit b2adf55674
2025-01-09 10:16:59 +00:00
4f01a120f7
[3.13] gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662) ( #128664 )
...
gh-79149: document reentrant safety of `loop.call_soon_threadsafe` (GH-128662)
(cherry picked from commit 4685401845
2025-01-09 09:25:18 +00:00
e5e70c5f09
Update documentation links to Microsoft's documentation pages (GH-126379)
...
(cherry picked from commit 6e25eb1541
2024-11-11 17:18:01 +00:00
05dcc81601
[3.13] gh-123517: Remove unnecessary `:meth:` parentheses (gh-123518) (GH-123577)
2024-09-02 16:00:04 +02:00
39f4add7a3
[3.13] gh-121333: Clarify what is the default executor for asyncio.run_in_executor (GH-121335) ( #121526 )
...
gh-121333: Clarify what is the default executor for asyncio.run_in_executor (GH-121335)
(cherry picked from commit facf9862da
2024-07-09 15:12:45 +05:30
206028dba9
[3.13] gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (GH-112191) ( #120935 )
...
gh-112169: Documented getaddrinfo/getnameinfo default loop executor usage and implications. (GH-112191)
(cherry picked from commit fc297b4ba4
2024-06-24 08:55:28 +00:00
8f31af68d0
[3.13] Format None, True, False and NotImplemented as literals (GH-118758) (GH-118792)
...
(cherry picked from commit 05c2fe1acd
2024-05-08 19:55:12 +00:00
4159644177
gh-113538: Add asycio.Server.{close,abort}_clients (redo) ( #116784 )
...
These give applications the option of more forcefully terminating client
connections for asyncio servers. Useful when terminating a service and
there is limited time to wait for clients to finish up their work.
This is a do-over with a test fix for gh-114432, which was reverted.
2024-03-18 13:15:53 -07:00
ba13215eb1
gh-113538: Revert "gh-113538: Add asycio.Server.{close,abort}_clients ( #114432 )" ( #116632 )
...
Revert "gh-113538: Add asycio.Server.{close,abort}_clients (#114432 )"
Reason: The new test doesn't always pass:
https://github.com/python/cpython/pull/116423#issuecomment-1989425489
This reverts commit 1d0d49a7e8
2024-03-12 00:31:49 +00:00
1d0d49a7e8
gh-113538: Add asycio.Server.{close,abort}_clients ( #114432 )
...
These give applications the option of more forcefully terminating client
connections for asyncio servers. Useful when terminating a service and
there is limited time to wait for clients to finish up their work.
2024-03-11 12:43:30 -07:00
808a77612f
gh-115664: Fix ordering of more versionadded and versionchanged directives (GH-116298)
2024-03-07 10:05:03 +02:00
0064dfa091
gh-115777: Fix double versionadded directives (GH-116269)
2024-03-05 17:41:53 +02:00
3aea6c4823
gh-101336: Add keep_alive keyword arg for asyncio create_server() ( #112485 )
2023-12-13 03:23:29 +00:00
74b868f636
gh-111246: Remove listening Unix socket on close ( #111483 )
...
Try to clean up the socket file we create so we don't add unused noise to the file system.
2023-11-08 08:10:10 -08:00
46389c3275
gh-101100: Fix sphinx warnings in `library/asyncio-eventloop.rst` (GH-111222)
...
* gh-101100: Fix sphinx warnings in `library/asyncio-eventloop.rst`
* Update Doc/library/socket.rst
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
* Update asyncio-eventloop.rst
* Update socket.rst
---------
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
2023-10-29 12:31:01 -07:00
2655369559
gh-79033: Try to fix asyncio.Server.wait_closed() again (GH-111336)
...
* Try to fix asyncio.Server.wait_closed() again
I identified the condition that `wait_closed()` is intended
to wait for: the server is closed *and* there are no more
active connections.
When this condition first becomes true, `_wakeup()` is called
(either from `close()` or from `_detach()`) and it sets `_waiters`
to `None`. So we just check for `self._waiters is None`; if it's
not `None`, we know we have to wait, and do so.
A problem was that the new test introduced in 3.12 explicitly
tested that `wait_closed()` returns immediately when the server
is *not* closed but there are currently no active connections.
This was a mistake (probably a misunderstanding of the intended
semantics). I've fixed the test, and added a separate test that
checks exactly for this scenario.
I also fixed an oddity where in `_wakeup()` the result of the
waiter was set to the waiter itself. This result is not used
anywhere and I changed this to `None`, to avoid a GC cycle.
* Update Lib/asyncio/base_events.py
---------
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
2023-10-28 18:04:29 +00:00
1198076447
gh-111151: Convert monospaced directives to :ref: ( #111152 )
2023-10-24 08:22:08 -07:00
8c689c9b88
gh-101100: Fix sphinx warnings in `library/asyncio-dev.rst` (GH-111179)
...
* gh-101100: Fix sphinx warnings in `library/asyncio-dev.rst`
* Update Doc/library/asyncio-eventloop.rst
* Update Doc/library/asyncio-eventloop.rst
---------
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
2023-10-22 17:11:57 +00:00
8c6c14b91b
gh-94597: Add asyncio.EventLoop ( #110723 )
...
This is needed to pave the way for deprecating and eventually killing the event loop policy system (which is over-engineered and rarely used).
2023-10-12 07:13:57 -07:00
13966da71b
gh-105857: Document that asyncio subprocess std{in,out,err} can be file handles ( #107986 )
...
stdin/out can be filehandles -> add to docs.
2023-08-22 20:41:56 +02:00
4b9948617f
gh-106909: Use role :const: for referencing module constants (GH-106910)
2023-07-21 12:40:37 +03:00
1e1f4e91a9
gh-106882: Note that `asyncio.Server` is only publicly exposed on 3.11+ ( #106901 )
...
And later versions of 3.10, 3.9
2023-07-19 20:56:26 +01:00
6b52a581c1
gh-105993: Add possible `None` return type to `asyncio.EventLoop.start_tls` docs ( #105995 )
2023-06-28 16:08:15 +05:30
68ed2a2a3f
GH-103484: Fix redirected permanently URLs ( #104001 )
...
Co-authored-by: Hugo van Kemenade <hugovk@users.noreply.github.com>
Co-authored-by: Oleg Iarygin <dralife@yandex.ru>
2023-05-02 09:34:44 +03:00
37e37553b0
gh-91441: Clarify the docs of asyncio.loop.subprocess_exec() ( #91442 )
...
Clarify the docs of asyncio.loop.subprocess_exec()
Clarify the documentation of stdin, stdout and stderr arguments of
asyncio.loop.subprocess_exec().
Co-authored-by: Carol Willing <carolcode@willingconsulting.com>
2023-04-26 12:57:19 -06:00
1c0a9c5a1c
gh-101786: Clarify docs that asyncio.Server.sockets is a socket-like TransportSocket ( #103877 )
...
Clarify that asyncio.Server.sockets is a socket-like TransportSocket
2023-04-26 06:32:24 -06:00
207e1c5cae
asyncio docs: Fix dangling hyphen ( #102227 )
...
Currently this gets rendered with a dangling hyphen.
2023-02-25 05:21:32 -08:00
c4de6b1d52
gh-85747: Active voice & suggested edits, 'running/stopping loop' & 'callbacks' subsections of asyncio-eventloop.rst ( #100270 )
...
Co-authored-by: C.A.M. Gerlach <CAM.Gerlach@Gerlach.CAM>
Co-authored-by: Terry Jan Reedy <tjreedy@udel.edu>
2023-02-06 21:25:42 -08:00
e5bd5ad70d
gh-100160: Restore and deprecate implicit creation of an event loop (GH-100410)
...
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>
2023-01-13 14:40:29 +02:00
5234e1cbea
gh-99830: asyncio: Document returns of remove_{reader,writer} ( #100302 )
2022-12-16 11:04:55 -08:00
fd38a2f0ec
gh-93453: No longer create an event loop in get_event_loop() ( #98440 )
...
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>
2022-12-06 18:42:12 +01:00
bf26bdf6ac
gh-85747: "Preface" section of asyncio-eventloop.rst: Switch to active voice and suggest other edits ( #99784 )
2022-12-03 16:48:41 -08:00
898d0d9ad8
gh-92679: Clarify asyncio.loop.start_tls parameters ( #92682 )
2022-11-01 21:52:19 -07:00
79fd6ccdbe
gh-85299: Add note warning about entry point guard for asyncio example ( #93457 )
2022-10-16 10:04:43 -07:00
74ea204634
GH-88968: Add notes about socket ownership transfers ( #97936 )
2022-10-05 16:42:01 -07:00
8079bef56f
GH-96704: Add {Task,Handle}.get_context(), use it in call_exception_handler() ( #96756 )
...
Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
2022-10-04 23:49:10 -07:00
53503ff60e
GH-82604: fix docs about configuring selector ( #97755 )
2022-10-04 09:45:37 -07:00
575a253b5c
GH-82448: Add thread timeout for loop.shutdown_default_executor ( #97561 )
...
Co-authored-by: Kyle Stanley <aeros167@gmail.com>
2022-09-28 10:39:42 -07:00
cc0f3a10f0
gh-96377: Update asyncio policy doc intro paras to be clear and accurate ( #97603 )
...
Also fix up some cross-references in the asyncio docs.
2022-09-27 16:47:14 -07:00
53a54b781d
gh-96706: [doc] Don't recomment deprecated use of get_event_loop() in examples ( #96707 )
2022-09-11 12:56:30 -07:00
a0ad63e70e
gh-93973: Add all_errors to asyncio.create_connection ( #93974 )
...
Co-authored-by: Oleg Iarygin <dralife@yandex.ru>
2022-09-04 18:33:50 -07:00
141f2517fc
gh-95767: Fix grammatical error in asyncio loop.create_task docs ( #95768 )
2022-08-09 15:59:27 +02:00
9523c0d84f
bpo-46994: Accept explicit contextvars.Context in asyncio create_task() API (GH-31837)
2022-03-14 13:54:13 +02:00
9f04ee569c
bpo-46805: Add low level UDP socket functions to asyncio (GH-31455)
2022-03-13 18:42:29 +02:00
41ddcd3f40
bpo-44011: Document ssl_shutdown_timeout added by revisited asyncio SSL implementation (GH-31597)
2022-02-26 15:06:43 +02:00
2923d87ca2
bpo-46777: Fix incorrect use of directives in asyncio documentation (GH-31388)
2022-02-18 10:58:48 +02:00
Thomas Grainger