newspaper
newspaper3k is a news, full-text, and article metadata extraction in Python 3. Advanced docs:
Runssource: GitHubhomepagePythonMITcommit f8e3cb63c87f
Python, MIT licensed. The project labels itself: crawler, crawling, news, news aggregator, python and scraper.
newspaper runs. An Argusic agent installed it in 1.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
newspaper3k 0.3.0 installs in a virtualenv on Python 3.12, all 40 unit tests pass, and core Article download/parse/nlp pipeline produces correct output from static HTML
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 100 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.
- lxml.html.clean module split into separate lxml_html_clean package0.3 minutes
- Chinese expected text file (tests/data/text/chinese.txt) contained overlong-encoded C2 93 / C2 94 bytes instead of proper UTF-8 curly quotes0.3 minutes
- NLTK punkt_tab resource missing (NLTK 3.10+ renamed punkt to punkt_tab)0.2 minutes
- Install time
- 2 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- `python -m pytest tests/unit_tests.py -v` exited 0, 40 passed, 5 skipped (the 5 skips are network-dependent: exhaustive, cache_categories, source_build, prepare_url, mthreading)
- Model tokens used
- 154,240
- Exact commit tested
- f8e3cb63c87f
- 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.
-现为间选议员的何俊仁说，梁振英至今仍不坦诚以对，让他震惊；亲北京政团工联会直选议员黄国健也批评梁振英抱着不服输的态度接受质询。 +现为间选议员的何俊仁说，梁振英至今仍不坦诚以对，让他“震惊”；亲北京政团工联会直选议员黄国健也批评梁振英抱着“不服输”的态度接受质询。 历时1.5小时的答问大会在进入中段之际，泛民主派人民力量的直选议员黄毓民、陈伟业和社会民主连线的梁国雄先后因播放录音、叫嚣，和向梁振英扔掷文件而被议长驱逐。 exec /bin/sh -lc 'cd /work/repo && git diff --stat 2>&1' in /work/repo succeeded in 0ms: tests/data/text/chinese.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) All clean. Let me produce the final report. tokens used 154,240 All clean. Let me produce the final report.
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.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Took 1.5 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 crawler projects Argusic has installed and timed, newspaper was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
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.5 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)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/newspaper)Questions
- Does newspaper run?
- Yes. newspaper runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test newspaper?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f8e3cb63c87f. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test newspaper?
- The run that produced this verdict cost $0.02: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does newspaper take to install?
- 1.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does newspaper need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing newspaper?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does newspaper compare with the alternatives?
- Of the 4 crawler projects Argusic has installed and timed, newspaper was the 3rd fastest to reach a running state, and 4 of 4 reached one at all.
- Where is the evidence for newspaper?
- 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.