Upgrade Python Project to Version 3.10 #18
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![gitar-bot-staging[bot]](https://avatars.githubusercontent.com/in/812680?s=60&v=4){kind=small}
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Migrate Python version from 3.9 to 3.10 across the entire codebase
Description
This PR migrates the project from Python 3.9 to Python 3.10 across all services, packages, and infrastructure components. The changes ensure consistent Python version usage throughout the codebase while maintaining compatibility and enabling access to Python 3.10 features.
Key Changes
setup.pyfiles to reflect Python 3.10 compatibilitypython_requiresfrom~=3.9to>=3.9,<3.11Programming Language :: Python :: 3.10Motivation
Impact
>=3.9,<3.11requirementFiles Modified
Complete list of modified files (46 total)
GitHub Actions Workflows
.github/workflows/ci-release.yml.github/workflows/ci-staging.yml.github/workflows/ci-testing-deploy.ymlPackages
packages/dask-task-models-library/setup.pypackages/models-library/setup.pypackages/postgres-database/setup.pypackages/service-integration/setup.pypackages/service-library/setup.pypackages/settings-library/setup.pyServices
services/agent/Dockerfile&setup.pyservices/api-server/Dockerfile&setup.pyservices/autoscaling/Dockerfile&setup.pyservices/catalog/Dockerfile&setup.pyservices/dask-sidecar/Dockerfile&setup.pyservices/datcore-adapter/Dockerfile&setup.pyservices/director-v2/Dockerfile&setup.pyservices/dynamic-sidecar/Dockerfile&setup.pyservices/invitations/Dockerfile&setup.pyservices/osparc-gateway-server/Dockerfile&setup.pyservices/storage/Dockerfile&setup.pyservices/web/Dockerfile&setup.pyScripts & Tools
requirements/tools/Dockerfilescripts/docker/docker-compose-config.bashscripts/erd/Dockerfilescripts/filestash/create_config.pyscripts/maintenance/migrate_project/Dockerfilescripts/mypy/Dockerfilescripts/pydeps-docker/DockerfileAdditional Files
packages/postgres-database/scripts/erd/Dockerfilepackages/service-library/src/servicelib/long_running_tasks/_task.pyservices/director/src/simcore_service_director/config.pyservices/director/src/simcore_service_director/producer.pyservices/migration/DockerfileTesting
All existing tests should continue to pass with Python 3.10. The migration maintains backward compatibility while enabling forward-looking development practices.
Related Links
Link to run
Requested by: [email protected]