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
Improve detection of async callables #1444
Improve detection of async callables #1444
Changes from all commits
ff314dd
a1c0764
636a26f
f6935c3
7312456
4151df6
8438a9f
788f011
dd8b7ed
7c74668
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.
Hi @Kludex, would it make sense to use
inspect.iscoroutinefunction
here?I understand why we cannot just use the said function alone, since
async def __call__(...)
is not captured by it:I have looked at the code of
asyncio.iscoroutinefunction
and it only additionally check for the deprecated@coroutine
decorator.Cheers,
Libor
This comment was marked as off-topic.
Sorry, something went wrong.