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
Cancelling TaskGroup.start()
cancels TaskGroup
itself (only for asyncio
backend)
#710
Open
2 tasks done
Open
2 tasks done
Labels
bug
Something isn't working
Comments
Isn't this a duplicate of #685? |
It might be, I don't really understand whether or not it's exactly the same. |
I think it probably at least stems from the same issue which I intend to fix for the next release. |
Thanks! That would be awesome. Feel free to close this or copy over the snippet as an additional test case if you prefer that. |
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Things to check first
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
AnyIO version
4.3.0
Python version
3.11.6
What happened?
Consider this snippet:
Here we spawn a task using
TaskGroup.start()
then we cancel the.start()
call usingmove_on_after
. It turns out this cancels the task group as a whole.I'd expect this to cancel only that particular task.
For the
trio
backend, this works fine, and does not cancel the task group.How can we reproduce the bug?
(see snippet above)
The text was updated successfully, but these errors were encountered: