scrapy
Scrapy, a fast high-level web crawling & scraping framework for Python.
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 08f0636b821c
Python, BSD-3-Clause licensed. The project labels itself: crawler, crawling, framework, hacktoberfest, python, scraping, web scraping and web scraping python.
scrapy runs. An Argusic agent installed it in 1 minute and hit 1 error on a clean machine with no GPU, and the whole session was recorded.
Scrapy 2.19.0 is installed and fully functional. The CLI, 4539/4540 tests, and an end-to-end crawl all work. The sole failing test is a container IPv6 limitation, not a code defect.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 80 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- test_download_conn_failed fails because container has IPv6 disabled; Twisted gets EADDRNOTAVAIL (errno 99) instead of ECONNREFUSED3 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 1 hit, 0 fixed with no human help
- How the result was proved
- pytest tests/ -k 'not test_download_conn_failed': 4539 passed, 446 skipped, 22 xfailed; real crawl against httpbin.org/anything returned 200, scraped 1 item; scrapy version printed Scrapy 2.19.0; scrapy help showed available commands
- Model tokens used
- 66,839
- Exact commit tested
- 08f0636b821c
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
**End-to-end crawl:** a real spider against `httpbin.org/anything` returned HTTP 200 and scraped 1 … **One container-bounded failure:** `test_download_conn_failed` hits `EADDRNOTAVAIL` (errno 99) inst… The ARGUSIC_RESULT line is printed above. tokens used 66,839 ## Summary **Scrapy 2.19.0** is installed and fully operational. **Install:** `pip install` in a fresh venv — all dependencies resolved cleanly. The `scrapy` CLI wo… **Tests:** `pytest tests/ -k "not test_download_conn_failed"` → **4539 passed**, 446 skipped, 22 xf… **End-to-end crawl:** a real spider against `httpbin.org/anything` returned HTTP 200 and scraped 1 … **One container-bounded failure:** `test_download_conn_failed` hits `EADDRNOTAVAIL` (errno 99) inst… The ARGUSIC_RESULT line is printed above.
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 1 minute.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Hit 1 error during setup, 1 of which were not solved.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
crawlercrawlingframeworkhacktoberfestpythonscrapingweb-scrapingweb-scraping-python
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/scrapy)Questions
- Does scrapy run?
- Yes. scrapy runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test scrapy?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 08f0636b821c. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test scrapy?
- The run that produced this verdict cost $0.04: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does scrapy take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does scrapy need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing scrapy?
- 1 thing broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for scrapy?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.