Fixes #9119: inject dispatch_uid for retry-wrapped receivers #9247
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.
Description
Fixes #9119 (or tries to)
This approach assumes we want to do the dispatch_uid calculation for the user behind the scenes, and that we want to handle both the decorator and non-decorator usecases for
signal.connect(receiver, sender=sender, retry=True)
Notes:
__wrapped__
(i.e.,functools.wraps(fun)(retry_over_time)
in decorator form), but this is a bit too generic for this type of solution, which may cause other issues