Fix #292: disuse HTTPResponse.strict #301
Merged
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 is an alternative PR to #294. It is more-or-less functionally equivalent to that PR. This alternative is being provided in case it turns out that the only reason #294 isn't being merged is that it includes formatting changes, etc. There are a couple of comments that indicate that might be the case. It seems that #292 affects a sufficiently wide collection of users that a timely fix is important.
Fixes #292
Fixes #293
What is here
strict
attribute from the HTTPRequest (de)serialization.test_etag.py
forrequests>=2.29
.Notes
As noted in this comment on #294, the
strict
parameter only has an effect if running under Python 2. Since cachecontrol no longer supports Python 2 there is no reason not to remove support forstrict
altogether (as is done here).