Skip to content

gh-108951: document how to terminate an asyncio.TaskGroup - #123837

Merged
gvanrossum merged 3 commits into
python:mainfrom
picnixz:docs/asyncio-task-group-cancel-108951
Sep 11, 2024
Merged

gh-108951: document how to terminate an asyncio.TaskGroup#123837
gvanrossum merged 3 commits into
python:mainfrom
picnixz:docs/asyncio-task-group-cancel-108951

Conversation

@picnixz

@picnixzpicnixz commented Sep 8, 2024

Copy link
Copy Markdown
Member

Credits to @sobolevn for the original implementation. I just reformulated a bit the way the tasks are created for the docs to make it a bit simpler (I think?)


📚 Documentation preview 📚: https://cpython-previews--123837.org.readthedocs.build/

@sobolevnsobolevn left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for polishing this! I am still not sure if this is worth adding to the docs or not. But, this is, luckily, up to asyncio maintainers to decide :)

@picnixz

Copy link
Copy Markdown
MemberAuthor

Yeah, I feel the same because the example is a bit artificial. Your example with randomness was probably closer to what people expect in practice, namely tasks that complete in a non-deterministic order and maybe one of them would want to cancel the entire group, but this also means a non-deterministic output (which I don't really want to have in the docs...).

As for playing the devil's advocate for this case, I don't see how we can "badly" use the helper, except if one explicitly changes the CancellableTaskGroup implementation (devil's advocates are welcomed by the way)

@Eclips4Eclips4 added needs backport to 3.12 only security fixes needs backport to 3.13 bugs and security fixes labels Sep 8, 2024
Comment threadDoc/library/asyncio-task.rst Outdated
Comment threadDoc/library/asyncio-task.rst Outdated
Comment threadDoc/library/asyncio-task.rst Outdated
Comment threadDoc/library/asyncio-task.rst Outdated
@picnixz

Copy link
Copy Markdown
MemberAuthor

Yeah, I feel the same because the example is a bit artificial

I knew it. When I was writing it I was like "hum... it's too long", so I wanted someone else's eyes, so thanks a lot for the comments Guido. I'll address them tomorrow

@picnixz
picnixzforce-pushed the docs/asyncio-task-group-cancel-108951 branch from 76942ed to 7c709b4CompareSeptember 9, 2024 12:51
@picnixz
picnixzforce-pushed the docs/asyncio-task-group-cancel-108951 branch from 7c709b4 to b4dc0bbCompareSeptember 9, 2024 12:52
@picnixz

Copy link
Copy Markdown
MemberAuthor

I kept the output because not everyone wants to run the code (sometimes, they just want to see the output). If you feel that neither the output nor the intermediate printing jobs are needed, please tell me. However, I think it's nice for the users to see a standalone working example.

@gvanrossumgvanrossum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Almost there! It looks nice and simple now.

Comment threadDoc/library/asyncio-task.rst Outdated

@picnixzpicnixz left a comment

Copy link
Copy Markdown
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A last bike-shedding question: would it make sense to also rename CancelTaskGroup into StopTaskGroup? strictly speaking, the exception serves as a signal to cancel/stop the task group (in the English sense) but we neither use CancelledError nor .cancel().

We would still use cancel in the docstring but to highlight the non-use of CancelledError, having a visually different name could be helpful for users (but it could also be confusing because they are close to each other...).

Comment threadDoc/library/asyncio-task.rst
Comment threadDoc/library/asyncio-task.rst Outdated

@willingcwillingc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I've added some suggestions.

Comment threadDoc/library/asyncio-task.rst Outdated
Comment threadDoc/library/asyncio-task.rst Outdated
@picnixz

picnixz commented Sep 11, 2024

Copy link
Copy Markdown
MemberAuthor

Maybe it's because I'm not an English native / asyncio expert, but I feel a slight difference with "terminate", "cancel", "stop" and "abort":

  • Cancel is kind of generic and can be used to convene the intent of "stopping" whatever is going on. In other words, it can mean "stop", "terminate", "abort" even though it does not use the cancellation in the asyncio sense.

  • Stop hints me that I could perhaps resume it later (though you could say it would have been a pause/resume). (A bit like SIGSTOP/SIGCONT).

  • Abort hints me that it's something abrupt and "not good". Like "abort the mission" or SIGABRT. It's more for an unexpected event.

I will go for terminate because:

  • it terminates/ends/cancels/finishes something,
  • it can be thought as SIGTERM which, when emitted, can be caught for a graceful exit (which is the case here, we literally catch the exception), and
  • it could be thought as the signal for reaching a "terminal" state where you wouldn't continue (in contrast to "stop").

@picnixz

Copy link
Copy Markdown
MemberAuthor

@willingc I took the liberty of rewording a bit the introductory paragraph. I quite like the While <some-unfortunate-thing>, we can <some-solution> construction.

@willingcwillingc left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @picnixz. I appreciate your work on this. I think this is ready for merge, but I will give other folks a little time for reviewing.

@gvanrossumgvanrossum left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Excellent! I will merge.

@gvanrossum
gvanrossum merged commit ef05801 into python:mainSep 11, 2024
@miss-islington-app

Copy link
Copy Markdown

Thanks @picnixz for the PR, and @gvanrossum for merging it 🌮🎉.. I'm working now to backport this PR to: 3.12, 3.13.
🐍🍒⛏🤖

miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 11, 2024
…onGH-123837)
We don't want to add another API, since the recipe is straightforward and rarely needed.
The advantage is that we could backport this to the earliest Python version that has taskgroups (3.11, alas in security mode already, so we'll just do 3.12 and 3.13).
(cherry picked from commit ef05801)
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
@bedevere-app

Copy link
Copy Markdown

GH-123956 is a backport of this pull request to the 3.13 branch.

@bedevere-appbedevere-appBot removed the needs backport to 3.13 bugs and security fixes label Sep 11, 2024
miss-islington pushed a commit to miss-islington/cpython that referenced this pull request Sep 11, 2024
…onGH-123837)
We don't want to add another API, since the recipe is straightforward and rarely needed.
The advantage is that we could backport this to the earliest Python version that has taskgroups (3.11, alas in security mode already, so we'll just do 3.12 and 3.13).
(cherry picked from commit ef05801)
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
@bedevere-app

Copy link
Copy Markdown

GH-123957 is a backport of this pull request to the 3.12 branch.

@bedevere-appbedevere-appBot removed the needs backport to 3.12 only security fixes label Sep 11, 2024
@gvanrossum

Copy link
Copy Markdown
Member

(Presumably the 3.13 backport will be held up by the upcoming release, unless the release manager deems doc PRs harmless. :-)

@picnixz
picnixz deleted the docs/asyncio-task-group-cancel-108951 branch September 11, 2024 15:47
@picnixzpicnixz changed the title gh-108951: document how to cancel an asyncio.TaskGroupgh-108951: document how to terminate an asyncio.TaskGroupSep 11, 2024
Yhg1s pushed a commit that referenced this pull request Sep 24, 2024
…123837) (#123956)
gh-108951: Document how to terminate an asyncio.TaskGroup (GH-123837)
We don't want to add another API, since the recipe is straightforward and rarely needed.
The advantage is that we could backport this to the earliest Python version that has taskgroups (3.11, alas in security mode already, so we'll just do 3.12 and 3.13).
(cherry picked from commit ef05801)
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
kumaraditya303 pushed a commit that referenced this pull request Sep 25, 2024
…123837) (#123957)
gh-108951: Document how to terminate an asyncio.TaskGroup (GH-123837)
We don't want to add another API, since the recipe is straightforward and rarely needed.
The advantage is that we could backport this to the earliest Python version that has taskgroups (3.11, alas in security mode already, so we'll just do 3.12 and 3.13).
(cherry picked from commit ef05801)
Co-authored-by: Bénédikt Tran <10796600+picnixz@users.noreply.github.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docsDocumentation in the Doc dirskip news

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

@picnixz@gvanrossum@1st1@willingc@sobolevn@Eclips4