Current PYRS workstreams and the artifacts that support them.
PYRS no longer treats internal roadmap/backlog docs as authoritative status. Current status is derived from
source, tests, and checked-in probe artifacts.
Current Workstreams
Workstream
Current focus
Release readiness
Installation polish, public docs accuracy, supported-platform packaging, and remaining pre-release hardening.
Runtime + stdlib long tail
CPython 3.14 parity closure across remaining stdlib/runtime edge behavior and mapped test gaps.
Native extensions + scientific stack
C-API lifetime-model closure, NumPy bring-up blockers, and broader extension compatibility for real workloads.
Performance + architecture
Observability, benchmark discipline, and deeper VM/runtime cleanup without regressing semantics.
How Closure Is Tracked
Workstream
Current focus
Runtime and stdlib compatibility
tests/cpython_harness.rs, tests/differential_cpython.rs, and perf/cpython_compat_benchmark_latest/.
Stdlib/runtime baselines
tests/stdlib_common_usecases.rs, perf/stdlib_compat_extended_latest.json, and perf/stdlib_full_probe_latest.json.
Language parity
docs/LANGUAGE_FEATURE_MANIFEST.json and the latest language coverage artifacts.
Native extensions/scientific stack
docs/EXTENSION_CAPABILITY_MATRIX.md, docs/NUMPY_BRINGUP_GATE.md, and perf/numpy_gate_direct_latest.json.
Historical Note
Area
Rule
Historical numbering
Old milestone terminology may still appear in commit history and notes, but it is no longer the primary status source.
Current practice
Use tests, headers, source modules, and checked-in artifacts for current status.
Why keep this page
It points at the evidence sources that currently define progress.
