pyosmium

Python bindings for libosmium

Runssource: GitHubhomepagePythonBSD-2-Clausecommit c4f1ae41f569

Python, BSD-2-Clause licensed. The project labels itself: openstreetmap and python.

pyosmium runs. An Argusic agent installed it in 22 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

Pyosmium 4.3.1 is built and installed in a virtualenv at /tmp/dev-venv; imports successfully, processes real OSM XML and PBF files correctly, all 401 tests pass, and the pyosmium-get-changes CLI tool reports version 4.3.1.

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

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.17 (measured)
recorded runs
1
last tested
stars
404
forks
81
open issues
13
watchers
12
size
24 MB
created
last push

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.

Time lost to each failure while testing pyosmium, 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.

  • CMake could not find Python Development.Module: /usr/include/python3.12 missing (python3-dev not installed)8 minutes
  • Linker failed on static libs (libz.a, libbz2.a) not compiled with -fPIC when building shared modules3 minutes
Install time
22 minutes
Cold machine to finish
20 minutes
Errors hit and fixed
2 hit, 2 fixed with no human help
How the result was proved
pytest test exited 0, 401 passed. /tmp/dev-venv/bin/pyosmium-get-changes --version printed 'pyosmium 4.3.1'. Python script processed /tmp/test.osm correctly (2 nodes, 1 way, 1 relation) and round-trip write/read to PBF (2 nodes, 2 ways). Examples osm_file_stats.py, convert.py, road_length.py, convert_to_geojson.py all ran correctly. Imported package reports pyosmium 4.3.1, libosmium 2.23.1.
Model tokens used
306,298
Exact commit tested
c4f1ae41f569
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.

- Initial file listing: ~02:44
- The pip install started at some point, and I had several failed attempts
- The build succeeded at some point
- Tests ran
- CLI tools verified
- Final verification complete
I estimate:
- Total elapsed: ~20-25 minutes
- Error 1 (Python headers): ~8 minutes
- Error 2 (Static library linking): ~3 minutes
- Tests + verification: ~5 minutes
Let me now write 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.
  • Installed in 22 minutes.
  • Recovered from all 2 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-2-Clause, 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.

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

tested byattemptoutcomescorecost USDwhen
Argusic Runner1/3Runs100.000.17

Topics (from GitHub)

openstreetmappython

Embed the badge

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

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

Questions

Does pyosmium run?
Yes. pyosmium runs. Argusic installed and launched it on a clean machine in 22 minutes, hitting 2 errors on the way, and recorded the session.
How did Argusic test pyosmium?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit c4f1ae41f569. One attempt is recorded, and the full method is on the methodology page.
What did it cost to test pyosmium?
The run that produced this verdict cost $0.17: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does pyosmium take to install?
22 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 pyosmium need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing pyosmium?
2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
Where is the evidence for pyosmium?
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.

Discussion