Put Python 3.15 Through Your Production Tests
Python 3.15.0 became stable on 9 October 2026. That closes the release-candidate wait, but it does not prove that your application stack is ready. Treat the new interpreter as a staged migration: reproduce production, exercise dependency installation, and promote only after the same workload passes.
Test text and import behaviour
Python 3.15 enables UTF-8 mode by default. Code that silently relied on the system locale can now read or write different bytes, with Windows the main compatibility concern identified by PEP 686. Run data imports, exports, command-line tools and logs with representative locale settings. Make encoding choices explicit where your format or environment requires them.
Lazy imports are explicit unless an application enables the global mode. They defer module loading, errors and import-time side effects until first use. Test plugin registration, monkey-patching, command discovery and failure paths. Keep modules eager where initialisation order matters, and measure your own startup path rather than assuming a general speed gain.
Verify wheels and native code
Create clean environments for every supported operating system and architecture. Confirm that the resolver finds Python 3.15 wheels, then force at least one source build in continuous integration where native extensions matter. Import each extension and run a service-level smoke test; a successful installer is only one checkpoint.
Python 3.15 adds a stable ABI for free-threaded builds. Extensions that cannot use it may still need separate abi3 and cp315t builds. Official Windows 64-bit binaries now use the tail-calling interpreter, while official macOS installers add free-threading support by default. Choose and benchmark the same build type you will deploy. Performance depends on the workload and build.
Scope the macOS warning
Python.org warns that IDLE and other Tk-based GUI applications can hang on macOS 27 when a menu command opens a dialog. This is a Tk workflow issue rather than a general Python 3.15 failure. Test affected desktop workflows before a macOS 27 rollout, or defer that operating system change until a workaround is available.
Make support part of the decision
PEP 790 plans bugfix releases about every two months for two years, followed by source-only security releases until about October 2031. Record the interpreter, ABI, dependency lock and rollback point with the deployment.
Track the Python 3.15 Lifecycle record, and keep older-branch risk separate in Python 3.10’s final patch does not keep it supported. A controlled migration gives the final release a production result that can be repeated and reviewed.
