kanban-python
Kanban Terminal App written in Python
Runssource: GitHubPythonMITcommit a50276bce61d
Python, MIT licensed. The project labels itself: cli app, kanban, kanban board application, kanban python, python and terminal based.
kanban-python runs. An Argusic agent installed it in 2.1 minutes and hit no errors on a clean machine with no GPU, and the whole session was recorded.
65 unit tests pass, the kanban CLI installs and runs with --help, --version, init, and configure all producing correct output
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.
- Install time
- 2 minutes
- Cold machine to finish
- 1 minutes
- Errors hit and fixed
- 0 hit, 0 fixed with no human help
- How the result was proved
- pytest tests/ exited 0, 65 passed; kanban --version returned 'kanban-python 0.6.4'; kanban init created a board and displayed the interactive kanban table; kanban configure displayed settings
- Model tokens used
- 84,283
- Exact commit tested
- a50276bce61d
- 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.
src/kanban_python/cli_parser.py 15 15 0 0 0% 1-64 src/kanban_python/config.py 114 7 8 2 93% 83-84, 114-115, 123-124, 152-… src/kanban_python/constants.py 24 0 0 0 100% src/kanban_python/controls.py 169 169 56 0 0% 1-340 src/kanban_python/interface.py 185 139 44 0 20% 33-61, 101-153, 158-166, 170,… src/kanban_python/utils.py 189 30 74 3 82% 46-47, 77->79, 86, 106-107, 1… TOTAL 751 409 206 5 42% ============================== 65 passed in 0.42s ============================== Everything works with zero errors. Here's the summary: tokens used 84,283 Everything works with zero errors. Here's the summary:
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 2.1 minutes, faster than the median of the 3 comparable projects Argusic has measured.
- Nothing broke on the way: zero errors between clone and running.
- 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
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 cli-app projects Argusic has installed and timed, kanban-python was the 2nd fastest to reach a running state, and 3 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 2.1 minutes after the clone.
- Following its own README: the documented path worked with nothing to fix.
Run history
Topics (from GitHub)
cli-appkanbankanban-board-applicationkanban-pythonpythonterminal-based
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/kanban-python)Questions
- Does kanban-python run?
- Yes. kanban-python runs. Argusic installed and launched it on a clean machine in 2 minutes, hitting 0 errors on the way, and recorded the session.
- How did Argusic test kanban-python?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a50276bce61d. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test kanban-python?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does kanban-python take to install?
- 2.1 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 kanban-python need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing kanban-python?
- Nothing did, in the recorded run: zero errors between clone and running.
- How does kanban-python compare with the alternatives?
- Of the 4 cli-app projects Argusic has installed and timed, kanban-python was the 2nd fastest to reach a running state, and 3 of 4 reached one at all.
- Where is the evidence for kanban-python?
- 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.