Python 3.15.0 Alpha 5: An Extra Developer Preview
Python 3.15.0 alpha 5 (3.15.0a5) is an additional early developer preview, released to correct a build issue with the previous alpha 4. This version gives developers a chance to test the latest new features and bug fixes ahead of the stable release. Below, we answer common questions about this snapshot and what it means for the Python community.
Why was Python 3.15.0a5 released as an extra alpha?
Alpha 4 (3.15.0a4) was accidentally compiled against a code snapshot from December 23, 2025, instead of the intended January 13, 2026. To ensure integrity and provide a build based on the correct branch state, the release team issued alpha 5, built against the proper January 14, 2026 code. This extra alpha ensures that early testers are evaluating the most current development work rather than a mix of old and new changes.
What is the purpose of Python 3.15 alpha releases?
Alpha releases like 3.15.0a5 serve as early developer previews of the upcoming Python version. They allow contributors, library maintainers, and advanced users to test new features, report bugs, and verify that the release process works smoothly. During the alpha phase (which runs until the beta phase begins on 2026-05-05), features may still be added, modified, or removed. Important: These builds are not recommended for production—they are made for experimentation and feedback.
What major new features are introduced in Python 3.15 so far?
Several significant enhancements are already included in alpha 5:
- PEP 799 – A new high-frequency, low-overhead statistical sampling profiler and a dedicated profiling package.
- PEP 686 – Python now uses UTF-8 as the default encoding for source files, improving cross-platform consistency.
- PEP 782 – Introduces a new
PyBytesWriterC API to simplify creating Python bytes objects.
Other improvements include better error messages and ongoing work on the JIT compiler (see next question). The list is still growing as the 3.15 series evolves.
How has the JIT compiler been improved in this alpha?
The just-in-time (JIT) compiler has received a significant upgrade. On x86-64 Linux, it delivers a 4–5% geometric mean performance improvement over the standard interpreter. On AArch64 macOS, the speedup reaches 7–8% compared to the tail-calling interpreter. These gains come from optimizations in code generation and inline caching, making Python faster without sacrificing compatibility.
What is the significance of PEP 686 regarding default encoding?
PEP 686 changes Python’s default source file encoding to UTF-8. Previously, Python used ASCII as the default (falling back to locale-dependent encodings). With this change, developers can use Unicode characters directly in source files without needing a # coding: utf-8 declaration. This aligns Python with modern practices, simplifies code portability, and reduces encoding-related bugs, especially on platforms that traditionally used different default encodings.
When is the next pre-release (3.15.0a6) scheduled?
Python 3.15.0a6 is currently scheduled for 2026-02-10. After alpha releases, the release process moves to beta (starting 2026-05-05) and then to release candidates (beginning 2026-07-28). You can track the full schedule in PEP 790.
Where can developers report bugs or find more resources?
Bugs should be reported on the CPython issue tracker at GitHub. The official online documentation covers the latest features. Developers can also support Python development directly via donations or by contributing to the Python Software Foundation. Release notes and downloads are available at python.org.