django-oscar
Domain-driven e-commerce for Django
Runssource: GitHubhomepagePythonBSD-3-Clausecommit 076197f4ccd5
Python, BSD-3-Clause licensed. The project labels itself: django, django oscar, ecommerce and oscar.
django-oscar runs. An Argusic agent installed it in 11 minutes and hit 4 errors on a clean machine with no GPU, and the whole session was recorded.
Package installed in venv, 1769 tests pass with SQLite, 4 pre-existing SQLite-specific failures remain, npm assets build successfully
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_updating_subtree_slugs_when_moving_category_to_new_parent: Category.full_slug cache polluted by prior test with same PK on SQLite5 minutes
- test_updating_subtree_when_moving_category_to_new_sibling: same root cause5 minutes
- test_single_usage: SQLite cannot handle concurrent writes for concurrency test5 minutes
- test_voucher_single_usage: same root cause5 minutes
- Install time
- 11 minutes
- Cold machine to finish
- 11 minutes
- Errors hit and fixed
- 4 hit, 0 fixed with no human help
- How the result was proved
- python -m pytest tests/ tests/unit --sqlite returned 1769 passed, 4 failed, 2 skipped
- Model tokens used
- 76,765
- Exact commit tested
- 076197f4ccd5
- 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.
- `test_single_usage` / `test_voucher_single_usage` — SQLite doesn't support concurrent writes (`Op… **Verified how**: Ran the full test suite via `python -m pytest tests/ tests/unit --sqlite` and obs… tokens used 76,765 Now let me compile the final result. The project is **django-oscar**, an e-commerce framework for Django. Here's the complete assessment: **Install**: `pip install -e ".[test]"` succeeded in a fresh venv. `npm install` and `gulp copy` bo… **Test suite**: Ran the full suite (`tests/` including unit, integration, functional) with SQLite b… **4 failures** — all pre-existing issues with SQLite: - `test_updating_subtree_slugs_when_moving_category_to_new_parent` / `_new_sibling` — Django's cach… - `test_single_usage` / `test_voucher_single_usage` — SQLite doesn't support concurrent writes (`Op… **Verified how**: Ran the full test suite via `python -m pytest tests/ tests/unit --sqlite` and obs…
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 11 minutes.
- 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 4 errors during setup, 4 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.
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/django-oscar)Questions
- Does django-oscar run?
- Yes. django-oscar runs. Argusic installed and launched it on a clean machine in 11 minutes, hitting 4 errors on the way, and recorded the session.
- How did Argusic test django-oscar?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 076197f4ccd5. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test django-oscar?
- 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 django-oscar take to install?
- 11 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 django-oscar need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing django-oscar?
- 4 things broke in the recorded run. Each one, and the time it cost, is listed on this page.
- Where is the evidence for django-oscar?
- 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.