Welcome to this early developer preview of Python 3.15.0 alpha 2, the second of seven planned alpha releases in the Python 3.15 series. This release offers a sneak peek at new features and bug fixes still under development. The following Q&A covers key details about this preview, its major new features, release schedule, and how you can get involved.

What is Python 3.15.0a2 and who is it for?

Python 3.15.0a2 is an early alpha release of Python 3.15, specifically the second alpha in the series. It is intended for developers who want to test the current state of new features and bug fixes, and to help validate the release process. This preview is not recommended for production environments. It gives the community a chance to experiment with upcoming changes and provide feedback before the final stable release.

What are the major new features in this alpha?

Several significant features are already included in alpha 2. Among them are three PEPs: PEP 799 introduces a high-frequency, low-overhead statistical sampling profiler along with a dedicated profiling package. PEP 686 makes UTF-8 the default encoding for Python. PEP 782 adds a new PyBytesWriter C API for creating Python bytes objects. Additionally, the release brings improved error messages that make debugging easier.

When is the next alpha and what is the release schedule?

Python 3.15.0a3 is the next pre-release, scheduled for 2025-12-16. The alpha phase will continue until the beta phase begins on 2026-05-05. Features may be added up to that date. After beta, the release candidate phase starts on 2026-07-28, during which only critical fixes are allowed. The final stable release is expected later in 2026.

Is this alpha suitable for production use?

No. Alpha releases like 3.15.0a2 are preview builds and should not be used in production environments. They are meant for testing and development only. Features may still change, be modified, or even removed before the final release. Production systems should wait for a stable version, typically the first release candidate or the final release.

What changes can be expected during the alpha phase?

During the alpha phase, features can be added, modified, or deleted up until the start of the beta phase. After that, only bug fixes and minor adjustments are permitted until the release candidate stage. This flexibility allows developers to refine the feature set based on testing and feedback. The alpha releases are a critical part of ensuring Python remains stable and polished.

How can developers get involved or report bugs?

Developers can help by testing the alpha and reporting bugs to the official issue tracker at github.com/python/cpython/issues. Feedback on new features is welcome. The release team also encourages contributions—either by volunteering or through organisational support to the Python Software Foundation. You can also fund Python directly or via GitHub Sponsors.

What is the significance of PEP 799?

PEP 799 introduces a high-frequency, low-overhead statistical sampling profiler for Python. This profiler is designed to provide detailed performance insights with minimal impact on execution speed. It includes a dedicated profiling package, making it easier for developers to identify bottlenecks and optimise their code. This is a major new tool for performance analysis in the Python ecosystem.

How does the new UTF-8 default encoding (PEP 686) affect users?

With PEP 686, Python now uses UTF-8 as the default encoding for source files and text handling. This change simplifies cross‑platform compatibility, as UTF-8 is widely adopted. It reduces encoding‑related errors and makes it easier to handle international characters. Existing code that relied on locale‑specific encodings may need minor adjustments, but overall this shift improves consistency and reduces subtle bugs.