Added constrain on lxml version to avoid error when using Python 3.4 (#3912) #3913
Conversation
This file contains 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
Fix ConfigParser import in py2
[MRG+1] docs for scrapy.logformatter
Log cipher, certificate and temp key info on establishing an SSL connection
fix default RETRY_HTTP_CODES value in docs
s3 file store persist_file should accept all supported headers
This was referenced Jul 30, 2019
Closed
|
#3918 is the correct PR. |
Gallaecio
approved these changes
Jul 30, 2019
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.
SUPERSEDED BY #3918
This fixes #3912 .
lxml 4.3.5 is the latest with Python 3.4 support.