RFC: Scrapy integration — optional Scrapling-style / adaptive parsing on responses #284
Replies: 4 comments 2 replies
-
|
Thanks for the suggestion, this is already in my mind |
Beta Was this translation helpful? Give feedback.
-
|
@D4Vinci Can you please provide your feedback on the feature PR. |
Beta Was this translation helpful? Give feedback.
-
|
@D4Vinci I see you have closed the PR as you have a better design. Can you please share your thoughts on your design. I'm very much interested to contribute. |
Beta Was this translation helpful? Give feedback.
-
|
I’ve simplified the Scrapy integration: instead of middleware and Scrapy settings that attach Scrapling to every response, it’s now a small optional helper. Call from_scrapy(response) when you want to parse with Scrapling, or use the @scrapling decorator on a callback so response is already a Scrapling object. Scrapy still handles crawling as before; this only adds a lightweight bridge when we need Scrapling’s parsing.No middleware or extra settings. Looking forward to collaborate with you on this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Feature description
Allow Scrapy users to opt into Scrapling’s parsing/adaptive selector behavior on
Responseobjects (e.g. middleware, decorator, or adapter), so they can keep Scrapy’s crawl pipeline while benefiting from Scrapling’s selection model when desired.Motivation
Proposal (high level)
response.selector/response.css/response.xpath.Non-goals (for v1)
Related
ROADMAP.md: “Create a Scrapy plugin/decorator…”Open questions
(I searched existing feature requests for this topic.)
Beta Was this translation helpful? Give feedback.
All reactions