-
-
Notifications
You must be signed in to change notification settings - Fork 34.5k
gh-96471: Add asyncio queue shutdown #104228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. Weβll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from 1 commit
440a702
fb458db
e5951ac
a72aedd
d5e925d
f3517fb
bd2a7c3
e9ac8de
1e7813a
1275bb6
eec29bb
2c6156f
17f1f32
a233830
420a247
25ad2ac
f3321b4
6d9edd6
1135d85
ddc6ad6
2fa1bd9
aef4063
d49c6dd
5a435a6
c8db40e
ca01ee1
b02c4dd
8deca77
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
- Loading branch information
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -102,14 +102,16 @@ Queue | |
|
|
||
| .. method:: shutdown(immediate=False) | ||
|
|
||
| Shut-down the queue, making queue gets and puts raise | ||
| :exc:`QueueShutDown`. | ||
| Shut down the queue, making :meth:`~Queue.get` and :meth:`~Queue.put` | ||
| raise :exc:`QueueShutDown`. | ||
|
|
||
| By default, gets will only raise once the queue is empty. Set | ||
| *immediate* to true to make gets raise immediately instead. | ||
| By default, :meth:`~Queue.get` on a shut down queue will only raise once | ||
| the queue is empty. Set *immediate* to true to make gets raise | ||
| immediately instead. | ||
|
|
||
| All blocked callers of put() will be unblocked, and also get() | ||
| and join() if *immediate* is true. | ||
| All blocked callers of :meth:`~Queue.put` will be unblocked. If | ||
| *immediate* is true, also unblock callers of :meth:`~Queue.get` and | ||
| :meth:`~Queue.join`. | ||
|
|
||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry but I have a doubt, shouldn't this documentation block be rather: In event of change, the docstring of the
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Also, I think the threading queue docs are the same.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
It's very precise, better.
Yes, I commented here so as not to forget (see #117532 (comment)). English is your native language, I think it'is best if you update documentations and docstrings. Update: but I can create the follow-up PR.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've made a PR: #117621 |
||
| .. versionadded:: 3.13 | ||
|
|
||
|
|
||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1 +1,2 @@ | ||
| Add asyncio.Queue termination with ``shutdown`` method. | ||
| Add :py:class:`asyncio.Queue`` termination with | ||
| :py:meth:`~asyncio.Queue.shutdown` method. |
Uh oh!
There was an error while loading. Please reload this page.