Python gets a post-quantum encryption library - the migration clock starts now

NIST's finalized post-quantum algorithms are now available as a Python package. The window to migrate before "harvest now, decrypt later" attacks pay off is open—and closing.

In plain terms: Python now has a native post-quantum cryptography library implementing NIST's finalized standards. Developers can start migrating cryptographic code today - before quantum machines become capable of breaking current encryption.

Why now matters

"Harvest now, decrypt later" is not a future threat - it's happening. Adversaries are already collecting encrypted traffic to crack retroactively once quantum computers scale. The practical implication: data encrypted today with RSA or ECDH that needs to remain confidential for 10+ years is already at risk. The Python library brings ML-KEM, ML-DSA, and SLH-DSA into the ecosystem as first-class packages, lowering the barrier to migration significantly.

Adoption speed will depend on framework integration. The maintainers of Python's core cryptography package are reportedly looking at incorporating post-quantum primitives, which would propagate support to Django, FastAPI, and the rest of the ecosystem.

Under the hood

The library implements ML-KEM (formerly CRYSTALS-Kyber for key encapsulation), ML-DSA (formerly CRYSTALS-Dilithium for signatures), and SLH-DSA (formerly SPHINCS+ for hash-based signatures) - the three algorithms NIST standardized in 2024. Key exchange requires more careful migration than signature replacement.

So what

If your Python service handles sensitive long-lived data - health records, financial transactions, legal documents - post-quantum readiness is now a concrete engineering task, not a theoretical future concern. Start with key exchange; that's where the exposure is highest.