Python 3.15.0 candidate 1 is here!

Python 3.15.0rc1 represents the transition from active development to stabilization. The core team has frozen the feature set and will now focus exclusively on fixing regressions or critical bugs. This shift means engineers can safely evaluate the release’s impact on their codebases without worrying about further breaking changes. The absence of ABI modifications from this point forward ensures that compiled extensions built against the release candidate will remain compatible with the final release, reducing the risk of last-minute rebuilds.

The call to action for third-party maintainers highlights the practical cost of adoption. Projects that delay testing until the final release may face bottlenecks if dependencies fail to publish compatible wheels in time. The Python Package Index (PyPI) will likely see an influx of 3.15-compatible packages during this phase, but teams should proactively verify their own dependencies. The performance gains, particularly the JIT compiler improvements, may justify early testing for latency-sensitive applications, but the preview nature of the release means production deployments should wait.

Several PEPs in this release introduce changes that could affect existing workflows. For example, the new `frozendict` built-in type and UTF-8 as the default encoding may require adjustments in code that relies on mutable dictionaries or legacy encoding assumptions. The stable ABI for free-threaded builds and frame pointers for observability suggest a focus on long-term maintainability, but these features may not be immediately relevant to all users. Engineers should prioritize testing areas where their projects intersect with the listed PEPs, particularly if they use profiling tools or type annotations.

The release candidate phase also serves as a documentation checkpoint. The core team’s emphasis on updating the “What’s New” section and ensuring proper documentation for changes implies that incomplete or missing documentation could delay the final release. For engineers, this means relying on official documentation rather than third-party sources during testing. The lack of a second release candidate in the schedule (only rc2 is planned) underscores the importance of reporting issues now, as there will be limited time to address them before the final release.