unstd
stdlib-faithful accelerated replacements. Each module wraps a native codec behind the call surface of the stdlib module it stands in for, so migrating a call site is an import swap, not a rewrite.
import json # →
from unstd.serde import jsonx # jsonx.dumps / jsonx.loads, same surface, faster
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
| Group | Extra | Backend / fallback |
|---|---|---|
serde |
unstd[serde] |
orjson / msgspec / pybase64 → stdlib json/base64 |
ids |
unstd[ids] |
uuid-utils → uid falls back to stdlib UUIDv7 |
crypto |
unstd[crypto] |
blake3 (required; hashlib ships BLAKE2, a different algorithm) |
time |
unstd[time] |
timeutil is pure stdlib; zoned requires whenever, and timeutil's protobuf Timestamp bridge requires unstd[proto] |
model |
unstd[model] |
pydantic (required) |
rex |
unstd[rex] |
irregex → stdlib re |
containers |
unstd[containers] |
sortedcontainers + immutables (required) |
rand |
unstd[rand] |
numpy PCG64 → stdlib random; crypto is always secrets |
pack |
unstd[pack] |
numpy → stdlib struct |
clone |
— | stdlib; exact-type walk, copy.deepcopy per foreign node |
text |
unstd[text] |
rapidfuzz → stdlib difflib |
audio |
unstd[audio] |
soundfile + numpy → stdlib wave |
toml |
unstd[toml] |
read is tomllib; write requires tomlkit |
proc |
— | stdlib subprocess |
fs |
— | stdlib os |
iters |
— | stdlib itertools |
clone, proc, fs, and iters ship in the base install.
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
1 maintainer
Metadata
1 maintainer
Release files for unstd 2.1.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| unstd-2.1.1.tar.gz | 346.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| unstd-2.1.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 484.0 kB
Release files / unstd-2.1.1.tar.gz
| Download URL | unstd-2.1.1.tar.gz |
|---|---|
| Size | 346.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ed39be938a3aa05a93f5329cad96b5b00f687dd528ed8a52e84ea487e7ef2d34
|
|
BLAKE2b-256 checksum How to use checksums |
c267c6d63185123d05bdc9b88bc9fe87a8b4b105e8c3eea873a2767d15017a2a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / unstd-2.1.1-py3-none-any.whl
| Download URL | unstd-2.1.1-py3-none-any.whl |
|---|---|
| Size | 137.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
99da9e671b8bcd484a1645ab3dd78403dfdc5a6fe7b79590e17fcd993476882c
|
|
BLAKE2b-256 checksum How to use checksums |
94340611a1735a3e9149098c7ba1a15ad424a0bf5f0f32e31e9a4416c287f959
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency log
