fix: keep Request and Response parameters per instance (1.2.1) - #21
Merged
Merged
Conversation
Request and Response stored their parameters in a class-level dict, so every instance in a process shared it: a parsed response could carry fields of a previous one, and a request could carry another customer's data. Each instance now gets its own dict, and known parameters that are absent read as None.
The release workflow publishes through Trusted Publishing when a v* tag is pushed, after checking the tag against [tool.poetry].version.
Version bump, changelog entry and pyproject metadata normalization (homepage and authors).
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
1 participant
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.
Summary
pypienvironment).Testing
python -m buildandtwine checkpass for the sdist and the wheel.