Python on BXM.net

BXM Canon 0.3.0 Adds Python, With Ints, Floats and Bytes Kept Apart and the Same Hash as Every Other Build

Thu, 22 Oct 2026 00:00:00 +0000

BXM Canon 0.3.0 adds a Python package. It’s the same Rust core again, this time called through PyO3, with wheels for Linux, macOS and Windows and any Python from 3.9 up. A value hashed in Python gives the hash the command line, the C library and the JavaScript package give, because all of them run the same code.

Python turned out to be the most natural fit so far. JavaScript has one number type, so a JavaScript caller has to think about whether 1 should be an integer or a float. Python already keeps int and float apart, and it has a real bytes type, which is exactly what Canon distinguishes. So the Python package can take a value straight from your program, no text step in between.

Hashing 100,000 JSON Lines Found No Duplicates, Hashing Them With Canon Found 9,900

Thu, 22 Oct 2026 00:00:00 +0000

Event pipelines get the same event twice. A producer times out, retries, and the retry goes through a different service that writes JSON its own way. The usual dedupe is a hash of each line, and it quietly misses all of these.

We generated a stream of 100,000 JSON lines from a fixed seed, 13.1 MB in all. 90,000 are distinct purchase events. The other 10,000 are resends of earlier events, written by two other producers. One sorts the keys and escapes non-ASCII, so “Zürich” arrives as Z\u00fcrich. The other reverses the key order and adds spaces. For a twist, 100 of the resends come from a producer that writes the quantity as a float: 2.0 where the original said 2.

One Order Built in Python, JavaScript and by Hand Gives Three JSON Hashes and One Canon Hash

Thu, 22 Oct 2026 00:00:00 +0000

A checkout service written in Python signs each order before it hands it on. A fulfilment service written in JavaScript checks the signature before it ships anything. Both have the same order in memory. The question is whether they agree on its bytes.

We built one order three ways. Python filled a dict in the order its code reads, and json.dumps wrote it with its defaults: a space after every comma and colon, and “Zürich” escaped as Z\u00fcrich. JavaScript built the same object with its keys in another order, and JSON.stringify wrote it compactly with the ü left as it is. The third copy is a file written by hand, pretty-printed, with yet another key order, hashed with the bxm-canon command.