{{ message }}
bpo-36918: Don't close the object which is again closed by destructor#13317
Closed
tirkarthi wants to merge 3 commits into
Closed
bpo-36918: Don't close the object which is again closed by destructor#13317tirkarthi wants to merge 3 commits into
tirkarthi wants to merge 3 commits into
Conversation
asvetlov
approved these changes
May 26, 2019
Member
Author
|
@asvetlov I would wait since Serhiy had a different opinion on this at https://bugs.python.org/msg342709 |
Sorry, something went wrong.
Member
|
Thanks a lot @tirkarthi for proposing this PR and identifying the root cause of these new errors. I merged PR #13996 which is similar (but different :-)) than your PR. |
Sorry, something went wrong.
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
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.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.
At the end of test
BytesIOdestructor is called that calls flush and close. Closing the object when the internal counter in FakeSocket gets to zero causes flush to be called on closed object in destructor. Mock the close function and let destructor do the work instead.https://bugs.python.org/issue36918