Update parsel dependency version to 1.8#201
Merged
Merged
Conversation
Coverage report
This PR does not seem to contain any modification to coverable code. |
The `lowest-direct` tests are failing because parsel 1.7 requires `pkg_resources` but didn't include it in its requirements. As requestium doesn't either, the minimum supported parsel version should be 1.8. parsel 1.8 release notes: https://github.com/scrapy/parsel/releases/tag/v1.8.0
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
2 participants
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.
The
lowest-directci tests are failing because parsel 1.7 requirespkg_resourcesbut didn't include it in its requirements. As requestium doesn't either, the minimum supported parsel version should be 1.8.parsel 1.8 release notes:
https://github.com/scrapy/parsel/releases/tag/v1.8.0
I also updated the dependency-review action because it was failing (it was using an old version of the action and missing a new endpoint from the firewall whitelist).