django-shop

A Django based shop system

Runssource: GitHubPythonBSD-3-Clausecommit 951d1e75b1f4

Python, BSD-3-Clause licensed. The project labels itself: django, django shop and e commerce.

django-shop runs. An Argusic agent installed it in 3 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 117 tests in the django-SHOP test suite pass with Python 3.12 and Django 3.0.14 in a virtual environment, using SQLite in-memory database with no external dependencies.

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 98.3 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
98.3 / 100
cost of the verifying run
$0.05 (measured)
recorded runs
2
last tested
stars
3,318
forks
0
open issues
0
watchers
0
created
-
last push
-

Subject data from GitHub, linked at the top of this page. 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.

Time lost to each failure while testing django-shop, drawn from the recorded run
Every bar is a failure the agent recorded, with the time it cost. Drawn from this run, not from anywhere else.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

  • pip install failed: externally-managed-environment (PEP 668) prevents system-wide install1 minute
  • Old django-allauth 0.40.0 fails to build with modern setuptools: ImportError cannot import name 'convert_path'1 minute
  • lxml 4.5.0 fails to compile on python3.12 (missing C headers)1 minute
  • pytest 5.3.1 crashes on Python 3.12: AttributeError: __spec__ from old py package1 minute
  • urllib3 1.25.9 missing packages.six.moves module1 minute
Install time
3 minutes
Cold machine to finish
5 minutes
Errors hit and fixed
5 hit, 5 fixed with no human help
How the result was proved
cd /work/repo/tests && /tmp/venv/bin/python -m pytest exited 0, 117 passed, collected and ran test_auth (11), test_cart (8), test_catalog (6), test_checkout (8), test_commodity (1), test_customer (6), test_inventory (3), test_order (2), test_auth again (1), test_deferred (29), test_money (30), test_money_db_field (4), test_enum (7), and test_cart again (1)
Model tokens used
125,057
Exact commit tested
951d1e75b1f4
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.

Script start: 1795342863
Let me calculate the elapsed time more carefully.
exec
/bin/sh -lc 'date +%s' in /work/repo
 succeeded in 0ms:
1795342865
The session started around timestamp 1795342863 (the first command was at or before that). It's now…
Let me compile the final result with proper timing. From the first install command to the test comp…
tokens used
125,057
The session started around timestamp 1795342863 (the first command was at or before that). It's now…
Let me compile the final result with proper timing. From the first install command to the test comp…

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 3 minutes, faster than the median of the 5 comparable projects Argusic has measured.
  • Recovered from all 5 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 BSD-3-Clause, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

Of the 6 django projects Argusic has installed and timed, django-shop was the 3rd fastest to reach a running state, and 5 of 6 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 3 minutes after the clone.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.05
Argusic Runner1/3Runs96.670.18

Topics (from GitHub)

djangodjango-shope-commerce

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/django-shop.svg)](https://argusic.com/subject/django-shop)

Questions

Does django-shop run?
Yes. django-shop runs. Argusic installed and launched it on a clean machine in 3 minutes, hitting 5 errors on the way, and recorded the session.
How did Argusic test django-shop?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit 951d1e75b1f4. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test django-shop?
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-shop take to install?
3 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-shop need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing django-shop?
5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does django-shop compare with the alternatives?
Of the 6 django projects Argusic has installed and timed, django-shop was the 3rd fastest to reach a running state, and 5 of 6 reached one at all.
Where is the evidence for django-shop?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion