-
-
Notifications
You must be signed in to change notification settings - Fork 858
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
Issue warning on unclosed AsyncClient
.
#1197
Merged
tomchristie
merged 7 commits into
encode:master
from
cdeler:prevent_async_client_from_sending_requests_when_its_closed
Sep 2, 2020
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
987b64a
Made Client and AsyncClient checking for being closed in __del__ (#871)
cdeler 22f663a
Changed the AsyncClient closing warning type from ResourceWarning (wh…
cdeler 8d85e87
Fixed tests and client's __exit__ and __aexit__ after the difficult m…
cdeler 44ba0b2
Merge branch 'master' into prevent_async_client_from_sending_requests…
tomchristie 0fd965a
Merge branch 'master' into prevent_async_client_from_sending_requests…
tomchristie d6e9be0
Update test_proxies.py
tomchristie c01e788
Update test_proxies.py
tomchristie File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
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.
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.
Right, I'm going to suggest that we use
UserWarning
for this case, for better visibility.We'll eventually end up tracking individual connections with proper a
ResourceWarning
against each of those, but this is a good case for a higher-level warning I think.Also, let's make sure to use a more concise warning format.
Perhaps...
Then we can add a little more context in the documentation.
What do we think?
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.
Developing libraries/SDKs, I try to avoid to use such warnings as
UserWarning
. This warning is for users' applications, not for a middle layer, presented by the SDK. Users should be able to separate their warning andhttpx
warnings.But I definitely agree with you, that
ResourceWarning
(unfortunately) is too silent for this case.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.
@tomchristie
I changed the warning type to
UserWarning
, then I have to fix a lot of warning in the project tests (it's a separated commit)