Python 3.10 reached its upstream end-of-life on October 1, 2026. The last security version is 3.10.22. There are no further upstream updates. Manufacturer support must be checked separately. The specific application compatibility should be tested individually.
Create a Project Inventory
Before a migration takes place, it is important to create a complete project inventory. This includes all used packages, dependencies, and the current version of the Python interpreter. This inventory helps identify potential compatibility issues early and plan solutions.
Check Manufacturer and Package Compatibility
Compatibility must be systematically checked, taking into account not only the Python version, but also all dependent libraries and their versions. External interfaces, such as database drivers or APIs, must be checked for support of the target version. For binary packages, platform and architecture compatibility is crucial. Planning should define clear responsibilities and maintenance windows to respond quickly to problems. It is important to divide migration steps into phases and check the impact on the entire application at each step. A wholesale migration without prior analysis can lead to unexpected errors.
Manufacturer information on supported versions is of central importance here.
Backup Application, Data, and Configuration
Before starting the migration, the application, data, and configurations should be fully backed up. The old environment must remain unchanged to be able to refer back to it in case of problems.
Test Project and Interpreter Check
The shown commands are Unix examples; all commands are executed in the root directory of a separate test project; relative paths refer to that. Before use, check the actual python3 version. The target version must already be installed, maintained, and project-compatible. No changes are made to productive services.
The test project serves for isolated testing of migration steps and should not be confused with production environments. Before starting the migration, determine the current Python version in the deployment environment and compare it with the target version. All commands in the test project are exemplary and serve demonstration purposes; they must be adapted to your own environment.
Before installation, the interpreter python3 must already be installed, maintained, and project-compatible. The file requirements-reviewed.txt is a self-prepared, tested package list for the target version and is not a provided file. The operating system Python must not be replaced. The global PATH must not be changed. Pervasive package upgrades are not recommended. The following commands should be used in the test project:
python3 --version
python3 -m venv .venv-next
.venv-next/bin/python -m pip install -r requirements-reviewed.txt
.venv-next/bin/python -m pip checkInstallation and Dependency Check
pip check only checks declared dependency compatibility. No application tests or security audits are performed. A venv isolates packages, but is not a security sandbox and does not resolve the end of support for the interpreter. Environments should be newly created, not copied or moved. Activation is not required if the interpreter path is explicitly named.
Testing and Rollback Planning
The acceptance of the migration should only take place if all planned tests have been successfully completed and no critical errors have occurred. Sensitive data must be handled according to project specifications to avoid risking violations of data protection regulations. Before the switch, document the expected results and compare them with the actual results. Differences must be documented in detail and not simply ignored.
After the installation and check of dependencies, the application, sample data, and external integrations should be tested. The criteria for the test must be documented. Existing environments, including the application and data backup, must be retained until acceptance. Only after that can a controlled switch be planned. A rollback to the old environment is only possible as an interim solution and does not restore full support.
For more information, see the official documentation: PEP 619, venv Documentation, pip check.