Python has released two expedited updates: Python 3.14.0rc2 and Python 3.13.7. The focus here is on 3.14.0rc2, the penultimate release candidate before the final stable release. This version introduces important changes, including a bytecode magic number bump that affects .pyc file compatibility. Below are common questions and detailed answers to help you understand the implications and prepare for the final release.

Why was Python 3.14.0rc2 released earlier than planned?

Originally scheduled for August 26, 2025, the release was moved up because a bug was discovered that required increasing the magic number stored in Python bytecode (.pyc files). This change means that .pyc files created with rc1 cannot be used with rc2 and will be automatically recompiled. To give the community extra testing time, the Python team decided to issue rc2 ahead of schedule. Additionally, a third release candidate (rc3) will be added to the timeline, with no change to the final release date.

How does the bytecode change affect .pyc files and compatibility?

The magic number bump means that any compiled bytecode files (.pyc) generated with the previous release candidate (rc1) are incompatible with rc2. When you run Python 3.14.0rc2, it will detect the mismatch and recompile the .pyc files automatically. This is a one-time cost and does not affect the source code or the application logic. The change is necessary to fix a bug, and it only impacts the internal bytecode format, not the Python language or standard library behavior.

Will existing wheels built for rc1 still work with rc2 and the final release?

Yes, binary wheels built for Python 3.14.0rc1 are fully compatible with rc2, rc3, and any future 3.14.x releases. The Application Binary Interface (ABI) remains unchanged throughout the 3.14 series. This stability means that if you have already published wheels for rc1, you do not need to rebuild them for rc2. The same applies to wheels built for any release candidate—they will work with the final version. This policy encourages early wheel publishing without worrying about future ABI breaks.

What is the new release schedule for Python 3.14?

Due to the early rc2 release, a third release candidate (rc3) has been added. The updated schedule is:

• Python 3.14.0rc2: released early (original date August 26, 2025)
• Python 3.14.0rc3: scheduled for September 16, 2025
• Final Python 3.14.0: scheduled for October 7, 2025

Only bug fixes are allowed between release candidates and the final release. No ABI changes will occur after this point, and code changes are minimized.

What are the major new features in Python 3.14?

Python 3.14 introduces several significant improvements over 3.13:

• PEP 779: Free-threaded Python is now officially supported, allowing true parallel execution without the Global Interpreter Lock (GIL).
• PEP 649: Deferred evaluation of annotations, improving semantics and reducing startup times.
• PEP 750: Template string literals (t-strings) for custom string processing with the familiar f-string syntax.
• PEP 734: Multiple interpreters in the standard library.
• PEP 784: A new compression.zstd module for Zstandard compression.
• PEP 758: The except and except* expressions can now omit brackets.
• Syntax highlighting in PyREPL, plus color support in unittest, argparse, json, and calendar CLIs.
• PEP 768: A zero-overhead external debugger interface for CPython.
• UUID versions 6–8 support and up to 40% faster generation for versions 3–5.

What is the call to action for third-party project maintainers?

Maintainers of third-party Python projects are strongly encouraged to test their libraries and tools with Python 3.14.0rc2 and publish compatible wheels on PyPI. Any binary wheels built against any release candidate will work with the final 3.14.0 release. By preparing early, you help the ecosystem be ready for the stable launch and enable other projects to conduct their own testing. Report any issues you find to the Python bug tracker. This is a preview release and not recommended for production environments, but it is close to the final version.

Is Python 3.14.0rc2 ready for production use?

No, Python 3.14.0rc2 is a preview release intended for testing and development. While it is very close to the final release, the Python team strongly advises against using it in production environments. Only bug fixes are applied between release candidates and the final release, but unforeseen issues may still exist. Use this version to validate compatibility, test your code, and report bugs, but wait for the official stable release (October 7, 2025) for production deployment.

What should core developers focus on now?

Core developers are asked to concentrate on documentation during this release candidate phase. Key questions to consider:

• Are all your changes properly documented?
• Are they mentioned in the "What’s New" guide?
• Have you noticed other changes that lack sufficient documentation?

Ensuring thorough documentation helps users and third-party developers understand the new features and transition smoothly. With the final release approaching, now is the time to polish explanatory texts, update examples, and clarify any ambiguous sections.