Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
add
@background_with_channel
#3197base: main
Are you sure you want to change the base?
add
@background_with_channel
#3197Changes from all commits
317cb1c
1a7714e
b0b8b02
8584cff
274755f
428dd4b
7542973
86d3b0f
2d11ea2
a5734f6
0b461d2
b86eb54
7936fd2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The loop in my prototype evolved from this one by @oremanj, via @belm0 here.
If we could trigger it, it'd have to be a non-
Cancelled
non-BrokenResourceError
, which occurred while waiting inawait send_chan.send(value)
. I think we could in principle get a few things here (e.g.KeyboardInterrupt
, GC-related errors, etc), but in each case calling.aclose()
on the generator and raising from this function without ever throwing the error into the generator seems like a reasonable response to me.So... I might be wrong, but this simpler code looks good to me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah since your version had
except
s forBrokenResourceError
andCancelled
it's only niche stuff that could get sent. And I don't see any reason why the generator should generate another value after thesend
gets cancelled or broken since it'll just fail again.Given that
send
has KI protection I don't even think it can raiseKeyboardInterrupt
(unless that gets raised just as the decorator exits? idk details how that works)