Add support for URLs in DUD_LOAD_RULE_PATHS. #15
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.
Fixes #1.
This uses
treq
for downloading, but there are many other options so this is open for discussion.requests
). Pros: synchronous requests simplify the code. Cons: synchronous may be bad?UrlCanonicalizer()
is currently decoupled from Scrapy.treq
. Pros: straightforward. Cons: additional dep.aiohttp
. Pros: just a more modern thing. Cons: additional dep, requires the asyncio reactor which is a blocker.Also this doesn't have tests for URLs, should we add mockserver, or wait until we publish the rules and use them in the tests?