Fix installation failure due to MarkupSafe and setuptools version conflict #17
Conversation
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.
Hi @fliot! Here's a small MarkupSafe-related bugfix:
Context
Deployment from
filot/ScrapyKeepermasterbranch would fail on Docker running inside Windows 10 because of MarkupSafe==1.0 requirement. It's incompatible with setuptools newer than v.46 (see pallets/markupsafe#116).Changes
Upgraded
MarkupSafeto 1.1.1 and upgraded the rest of dependencies to latest version.Testing
Deployed
ScrapyKeeperto Alpine Linux docker containers, hosted on Ubuntu 18.0.4 and Windows 10 machines, deployed ascrapydegg, ran a smoke test crawl. Looks like everything's working and upgrading didn't break anything.