Welcome to the latest snapshot of Python 3.15 development! This alpha release, version 3.15.0a5, offers a glimpse into exciting new features and performance upgrades. Below, we answer the most pressing questions about what this release brings, why it exists, and what to expect next.

What is Python 3.15.0 alpha 5 and why was it released?

Python 3.15.0 alpha 5 is the fifth of seven planned alpha releases for the upcoming Python 3.15 series. It was issued as an extra release because its predecessor, 3.15.0a4, was accidentally built against an outdated version of the main branch (2025-12-23 instead of 2026-01-13). This alpha 5 corrects that error, being built against the proper 2026-01-14 codebase. As an early developer preview, it is intended for testing new features and bug fixes, and is not recommended for production environments. The alpha phase allows features to be added, modified, or removed until the beta phase begins on May 5, 2026, and the release candidate phase on July 28, 2026.

What are the major new features planned for Python 3.15?

Several significant enhancements are already in the pipeline for Python 3.15. Among them are three PEPs: PEP 799, which introduces a high-frequency, low-overhead statistical sampling profiler and a dedicated profiling package; PEP 686, which changes Python's default encoding to UTF-8; and PEP 782, which adds a new PyBytesWriter C API for creating Python bytes objects. The JIT compiler has also received a major upgrade, delivering a 4-5% geometric mean performance improvement on x86-64 Linux over the standard interpreter, and a 7-8% speedup on AArch64 macOS over the tail-calling interpreter. Additionally, error messages have been improved. (If you’re a core developer and notice a missing feature, please inform Hugo van Kemenade.)

What is the purpose of alpha releases and when is the beta phase?

Alpha releases like 3.15.0a5 serve as early developer previews. They allow the community to test the current state of new features and bug fixes, as well as the release process itself. During the alpha phase (which runs until May 5, 2026), features may be added, modified, or even deleted. After that, the beta phase begins, followed by the release candidate phase starting July 28, 2026. Throughout these phases, the code becomes increasingly stable and feature-frozen. The next pre-release is scheduled for February 10, 2026: 3.15.0a6. All dates are subject to change, so check PEP 790 for the official release schedule.

How does the JIT compiler performance improve in Python 3.15?

The JIT (Just-In-Time) compiler in Python 3.15 has been significantly upgraded. Benchmarks show a 4-5% geometric mean performance improvement on x86-64 Linux when compared to the standard interpreter. On AArch64 macOS, the speedup is even more pronounced: 7-8% faster than the tail-calling interpreter used in earlier versions. These gains come from optimizations in code generation and compilation strategies. While not a revolutionary leap, this steady improvement helps Python better compete with lower-level languages for performance-sensitive tasks. The JIT remains optional and is designed to accelerate long-running applications without compromising Python's dynamic nature.

What is PEP 799 about?

PEP 799 proposes a new statistical sampling profiler for Python. Unlike traditional profilers that instrument every function call (which can slow down execution), this profiler uses a high-frequency, low-overhead approach. It periodically samples the call stack, providing statistical insights into where time is spent. The profiler comes bundled with a dedicated profiling package, making it easy for developers to integrate into their workflow. This tool is especially useful for analyzing production systems where minimal performance impact is critical. By collecting data at a high sampling rate, it can accurately pinpoint bottlenecks without distorting runtime behavior. Early testing suggests it offers a better balance between detail and efficiency compared to existing profilers.

What changes does PEP 686 bring?

PEP 686 makes UTF-8 the default encoding for Python. Previously, the default encoding was platform-dependent (often ASCII or locale-specific). This change aims to reduce confusion and bugs related to character encoding mismatches, especially when dealing with text files and network data. With UTF-8 as the default, Python will assume all text is UTF-8 encoded unless explicitly stated otherwise. This aligns Python with modern web standards and simplifies internationalization. The PEP also includes a transition period and guides for handling legacy systems that rely on non-UTF-8 defaults. Developers are encouraged to update their code to explicitly specify encodings where needed, but the new default will gradually become the norm.

What is PEP 782?

PEP 782 introduces a new PyBytesWriter C API for creating Python bytes objects. This C-level interface allows efficient, incremental construction of bytes objects without the overhead of repeatedly copying data. It’s designed for extension writers and internal CPython modules that need to build bytes from chunks (e.g., when serializing data or reading from streams). The API provides methods to write raw bytes, reserve space, and finalize the object. This addition aims to improve performance in scenarios where bytes are assembled piecemeal, reducing memory allocation and copying overhead. It’s a low-level enhancement that will benefit many parts of the Python ecosystem, especially networking, file I/O, and binary data processing.

When is the next pre-release of Python 3.15 scheduled?

The next pre-release in the Python 3.15 series will be 3.15.0a6, currently scheduled for February 10, 2026. This will be followed by two more alpha releases, then the beta phase. The Python release team (Hugo van Kemenade, Ned Deily, Steve Dower, and Łukasz Langa) encourages everyone to test the alphas and report bugs at the CPython issue tracker. Funding and volunteering are also welcome—visit the Python Software Foundation’s site to learn how to contribute. Enjoy the release and share your feedback!