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 just an idea I had that I would like to discuss.
I've seen that the
requests-html
library adds alinks()
method to extract all the URLs in the HTML. In parsel you can easily extract the links by usingcss()
orxpath()
, but there could be some logic that could be simplified by creating alinks()
method (see code).A possible use would be to use it in conjunction with
scrapy.Response.follow_all()
to easily crawl all URLs in the HTML.Of course, this should be refactored, properly documented, and tested. Or even converted to a generator. We could also exclude other URL patterns like
tel:
or even add a method parameter to filter the URLS (by a regex pattern like we do inscrapy.sitemap.SitemapSpider
?) or implement an option to get the absolute links.So I would like to know what you think about this, if you think it's useful or not and if it should be implemented or not (or alternatively, if it should be implemented directly into the
scrapy.selector.Selector
) 🙂Resolves #26