Drop RuntimeError on closing a connection pool with active connections.#631
Merged
lovelydinosaur merged 6 commits intomasterfrom Dec 14, 2022
Conversation
…ool-with-open-connections
…ool-with-open-connections
Contributor
Contributor
Author
…ool-with-open-connections
zanieb
reviewed
Dec 8, 2022
zanieb
approved these changes
Dec 14, 2022
…ool-with-open-connections
Contributor
Author
|
Thanks @madkinsz 👍 |
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.
Closes #564.
Closes #561 (The motivation given there becomes redundant. Errors will be raised against the connections themselves)
With this script...
example.py:
Before this change...
After this change...
But, if we attempt close the connection pool and then later attempt to read from a connection, we will still get sensible behaviour...
example.py:
Output: