post-quantum-crypto ml-kem ml-dsa pyca-cryptography nist-standards

Post-quantum cryptography lands in pyca/cryptography

ML-KEM and ML-DSA are now available in cryptography>=48, enabling Python applications to migrate away from classical primitives — but you'll need to rework wire formats since PQ keys and signatures are 1–2 orders of magnitude larger.

Summary

pyca/cryptography is the eleventh most-downloaded PyPI package with 1.2 billion monthly downloads; if it doesn't expose PQ algorithms, the entire Python ecosystem stalls on quantum-resistant migration. Federal deadlines (key establishment by 2030, signatures by 2031) will force this transition, starting now with library support.

Why it matters

Implementation verdict

Replaces Ed25519/X25519 with ML-DSA-65 and ML-KEM-768 respectively. Requires protocol redesign: public keys grow from 32B to 1,184–1,952B, signatures from 64B to 3,309B. API mirrors existing asymmetric patterns, so adoption is straightforward for new code. Not a drop-in swap for existing protocols due to size explosions. Worth trying now in new designs; defer in production until protocols (TLS, certificate formats) add native support.

Sources

1.Almost every Python program that touches cryptography goes through pyca/cryptography
2.It's currently the eleventh most-downloaded package on PyPI, pulling 1.2 billion downloads in the last month alone
3.As of cryptography>=48, support for post quantum algorithms is just a pip install away
4.Public keys, signatures, and ciphertexts are often 1–2 orders of magnitude larger than the classical values they replace
5.high-value and high-impact federal systems must use post-quantum key establishment by December 31, 2030, and post-quantum digital signatures by December 31, 2031

Dev Signal

Get briefs like this in your inbox — free, every weekday.

100+ sources compressed into one 4-minute read. Ranked, cited, implementation-ready.

Read the full issue →All briefs