Breaking: Python 3.15 Alpha 4 Released – But a Build Error Triggers an Unexpected Extra Alpha
The Python Software Foundation has released Python 3.15.0a4, the fourth of seven planned alpha releases for the upcoming 3.15 series. However, a critical build error has already forced the team to schedule an additional 3.15.0a5 release for February 10, 2026.
“This alpha was accidentally built against the main branch from December 23, 2025, instead of January 13, 2026,” explained Hugo van Kemenade, Python release manager. “We discovered the mistake after publication and are issuing 3.15.0a5 to ensure testers work with the correct codebase.”
All users testing the alpha are strongly urged to upgrade to 3.15.0a5 when it becomes available. The current alpha remains usable but may contain inconsistencies.
Key New Features in Python 3.15 so Far
Despite the hiccup, 3.15.0a4 introduces several major changes:
- PEP 799 – A new high-frequency, low-overhead statistical sampling profiler and dedicated packaging.
- PEP 686 – Python now defaults to UTF-8 encoding across the board.
- PEP 782 – A new
PyBytesWriterC API for efficient creation of Python bytes objects. - JIT compiler upgrades – Up to 3‑4% geometric mean speedup on x86‑64 Linux, and 7‑8% on AArch64 macOS compared to the tail-calling interpreter.
- Improved error messages – More precise and helpful runtime diagnostics.
Background: What Alpha Means
Python 3.15 remains in active development. Alpha releases like 3.15.0a4 are intended for early testing of new features and bug fixes. Features may be added or modified until the beta phase begins on May 5, 2026, and deletions remain possible until the release candidate phase on July 28, 2026.
These builds are not recommended for production environments. Developers are encouraged to test their code against the alpha to identify regressions and provide feedback to the core team.
What This Means for Developers
If you maintain Python libraries or applications, now is the time to start testing against 3.15. The JIT improvements alone could significantly boost performance for CPU‑bound workloads, especially on ARM Macs. The UTF-8 default (PEP 686) may affect code that assumes a different encoding for file I/O or data processing.
“The fastest way to help shape this release is to test your projects against the alpha series and file issues on the CPython bug tracker,” van Kemenade noted. “Every report makes the final release more robust.”
For a complete list of changes and the full release schedule, see PEP 790 and the official download page.