unstd

stdlib-faithful replacements, with optional native acceleration where it preserves the contract. Modules follow the stdlib call surface, so migrating a call site is an import swap. JSON proves native eligibility and falls back to stdlib codecs to preserve formatting, values, callbacks and errors.

import json  # →
from unstd.serde import jsonx  # faithful json API; dumpb for compact transport

The base install is pure stdlib: depending on unstd adds zero third-party closure. Every accelerated backend rides an optional extra with a guarded import that falls back to the stdlib (or raises a clear ImportError where no fallback is faithful). Install unstd and you pay nothing. Install unstd[serde] and the serde modules light up.

Install

python3 -m pip install unstd
python3 -m pip install 'unstd[serde,ids,crypto]'

Groups

clone, proc, fs, and iters ship in the base install.

Testing

The test suite follows Billy's owner-first Python layout: product contracts, cross-cutting assurance, shared support, and standalone tools. The P0 boundary suites exercise installed packaging, real TLS peers, filesystem/process failures, and parser/token security. The coverage plan maps parity, properties, fuzzing, penetration, fault injection, packaging, concurrency, resource, and performance obligations. Inspect implemented and planned lanes with uv run --no-sync python -m tests.tooling list; run the active suite with uv run --no-sync pytest -q.

The fuzz runner supplies eleven parser/token targets, authenticated corpora, deterministic mutation, and bounded Atheris campaigns. Run uv run --no-sync python -m tests.tooling.fuzz check to validate the inventory, or uv run --no-sync python -m tests.tooling.fuzz replay to replay every installed target. CI retains findings and coverage corpora.

The chaos runner exercises recorded filesystem, process, stream and clock/entropy failures and recovery. Run uv run --no-sync python -m tests.tooling.chaos run --seed 173 for a bounded installed-backend campaign with per-case journals and reproducible schedules.

The concurrency runner checks atomic file histories, UUID contention and fork safety, and shared cache/parser isolation. Run uv run --no-sync python -m tests.tooling.concurrency run --seed 173 for bounded installed-backend workers with retained histories and replay.

Prior art

• orjson (Kloss) / msgspec (Fitzgerald) / pybase64 (aklomp libbase64) — the serde backends.
• The guarded-optional-backend pattern is the one uvloop popularized: import the accelerator, fall back when it is absent.

License

Apache-2.0