Introduction

This guide takes you through the process of downloading, installing, and testing Python 3.15.0 alpha 5 — a special extra preview release that corrects a build issue from alpha 4. As an early developer preview, this release is designed to help you explore upcoming features and provide feedback before the final stable version. Follow these steps to safely evaluate the new capabilities without disrupting your production environment.

What You Need

• Python 3.15.0a5 installer – available from the official Python downloads page at python.org/downloads/release/python-3150a5/
• A compatible operating system – Windows, macOS, or Linux
• Basic familiarity with the command line – for creating virtual environments and running tests
• A test project or script – to evaluate compatibility and new features
• A bug reporting account (optional) – at GitHub CPython issues

Step-by-Step Instructions

Step 1: Download Python 3.15.0 Alpha 5

Visit the Python 3.15.0a5 release page and download the appropriate installer for your operating system. This alpha release is not recommended for production environments; it is intended for testing and development previews only. Note that this is an extra alpha (a5) because alpha 4 was accidentally built against a December 2025 main branch instead of the January 2026 branch. Alpha 5 is built correctly against 2026-01-14 sources.

Step 2: Install in an Isolated Environment

To avoid interfering with your system Python, install this alpha release in a separate location or use a virtual environment. On Unix-based systems, you can extract the tarball and run ./configure --prefix=/path/to/test followed by make and make install. On Windows, use the installer and choose a custom installation path. Alternatively, use pyenv to manage multiple Python versions. After installation, verify the version by running python3.15 --version — it should display Python 3.15.0a5.

Step 3: Explore Major New Features

Python 3.15 introduces several significant changes. Familiarize yourself with the following key additions:

• PEP 799 – Statistical Sampling Profiler: A high-frequency, low-overhead profiler that uses statistical sampling. Test it by running your code with the new -m profile module or the dedicated pyperf package.
• PEP 686 – UTF-8 Default Encoding: Python now uses UTF-8 as the default encoding. Check that your text I/O still works correctly, especially if your code relied on the previous locale-dependent behavior.
• PEP 782 – PyBytesWriter C API: A new C API for building Python bytes objects efficiently. If you write C extensions, test any code that creates bytes objects.
• JIT Compiler Improvements: The just-in-time compiler has been upgraded, offering 4-5% speed improvement on x86-64 Linux and 7-8% on AArch64 macOS over the standard interpreter. Run benchmarks to see the difference.
• Improved Error Messages: Many error messages have been clarified and enhanced. Pay attention to any new diagnostics in your test runs.

Step 4: Test Your Code and Report Issues

Run your existing projects or a representative test suite under Python 3.15.0a5. Look for:

• Deprecation warnings or changed behavior (especially around encoding and profiling)
• Compatibility issues with third-party packages — use pip install in the test environment to check
• Performance regressions or improvements

If you encounter bugs, report them at the CPython issue tracker. Include your platform, Python version, and a minimal reproduction script. The release team appreciates all feedback that helps improve the final release.

Step 5: Engage with the Community

Consider contributing to Python’s development. You can help by:

• Volunteering your time to fix bugs or write documentation
• Supporting the Python Software Foundation financially via direct donations or GitHub Sponsors
• Joining discussions on the Python developer mailing list

Step 6: Stay Updated

The next pre-release, Python 3.15.0a6, is scheduled for 2026-02-10. Monitor the release schedule in PEP 790 and look out for beta releases starting 2026-05-05. Note that features may be added, modified, or removed until the release candidate phase on 2026-07-28.

Step 7: Clean Up After Testing

Once you’ve completed your evaluation, you can safely remove the alpha installation by deleting the directory or uninstalling the package. Remember to revert to your stable Python version for production work.

Tips for Success

• Always use a virtual environment when testing alpha releases to avoid corrupting your system Python.
• Do not use this release in production. Alpha versions are unstable and may contain critical bugs.
• Test early, test often — the earlier you report issues, the more likely they’ll be fixed before the final release.
• Read the online documentation (linked from the download page) for in-depth details on new features.
• Share feedback with the core developers via the issue tracker or developer mailing list. The quote from the release notes says: “if a feature you find important is missing from this list, let Hugo know.”
• Back up your work before running any alpha software.