puput
A Django blog app implemented in Wagtail
Runssource: GitHubPythonMITcommit ce7a2f5293c4
Python, MIT licensed. The project labels itself: blog, blogging, cms, django and wagtail.
puput runs. An Argusic agent installed it in 12 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The test suite passes (8 passed) and the live dev server serves the blog homepage, RSS feed, an entry page, tag/category/list URLs, and the admin login page over HTTP in this container.
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.
- Committed tests/testapp/puput.db is an old Wagtail/SQLite schema; live GETs hit 'no such column translation_key' and entry creation hit 'NoneType _inc_path' and Document DoesNotExist20 minutes
- pytest-django: No module named 'tests' — PYTHONPATH not set2 minutes
- auth_user UNIQUE constraint during live entry-creation scripting (legacy admin row present)1 minute
- Install time
- 12 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- pytest exited 0, 8 passed, 10 warnings; runserver started, curl/Client returned 200 on /, /blog/, /blog/feed/, /blog/my-test-entry/, /blog/2026/10/16/my-test-entry/, /blog/tag/foo/, /blog/category/cat1/, /blog_admin/login/; feed contained 'My test entry'
- Model tokens used
- 862,774
- Exact commit tested
- ce7a2f5293c4
- 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.
862,774
Done. Here is the report.
**What I did**
- Read `README.rst` and `docs/setup.rst`, then installed per docs: `pip install -e .` plus `require…
- Ran `pytest` per `tox.ini` and exercised the app live via Django's dev server plus `django.test.C…
**Errors hit and fixes**
- `pytest-django: No module named 'tests'` — repo's tox sets `PYTHONPATH={toxinidir}`; the README d…
- `EntryPage.add_child` raised `AttributeError: 'NoneType' object has no attribute '_inc_path'`, an…
- Error three (repeated): `UNIQUE constraint failed: auth_user.username` when scripting its live (f…
**Final state**
- `git status` shows only `tests/testapp/puput.db` modified (schema migrated from the legacy commit…
- Live server run: `runserver` started cleanly at `127.0.0.1:8000`; live HTTP checks: `/` 200, `/bl…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 12 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 blog projects Argusic has installed and timed, puput was the 8th fastest to reach a running state, and 11 of 11 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.
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/puput)Questions
- Does puput run?
- Yes. puput runs. Argusic installed and launched it on a clean machine in 12 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test puput?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit ce7a2f5293c4. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test puput?
- The run that produced this verdict cost $0.05: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does puput take to install?
- 12 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 puput need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing puput?
- 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 puput compare with the alternatives?
- Of the 11 blog projects Argusic has installed and timed, puput was the 8th fastest to reach a running state, and 11 of 11 reached one at all.
- Where is the evidence for puput?
- 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.