fix: Refine async_timeout to properly handle TypeVar usage#185
Merged
filipchristiansen merged 1 commit intomainfrom Feb 17, 2025
Merged
fix: Refine async_timeout to properly handle TypeVar usage#185filipchristiansen merged 1 commit intomainfrom
filipchristiansen merged 1 commit intomainfrom
Conversation
24ee721 to
ba2f385
Compare
ba2f385 to
46bed45
Compare
cyclotruc
approved these changes
Feb 17, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR updates the
async_timeoutfunction signature to address a Pylance warning aboutTypeVarusage. Specifically, the function definition has been changed from: