chore(python): bump Python runtime from 3.9 to 3.11#9005
Open
DoDiODev wants to merge 1 commit into
Open
Conversation
Bump the Python runtime used across the project from 3.9 to 3.11: - backend/Dockerfile: server image base python:3.9 -> python:3.11 - backend/python/uv.sh: default uv venv python 3.9 -> 3.11 - pydevlake / azuredevops / fakeplugin pyproject.toml: python constraint "~3.9" -> ">=3.11,<3.12" - .devcontainer/devcontainer.json: python feature 3.9 -> 3.11 - backend/python/DevelopmentSetup.md: docs reference python3.11 This is a pure runtime bump. No library versions are changed and the existing Pydantic v1 code keeps working on 3.11 (verified with build-pydevlake and unit-test-python). Library upgrades (Pydantic v2, SQLModel, ...) and the corresponding poetry.lock regeneration are done in a follow-up PR. Signed-off-by: DoDiODev <DoDiDev@proton.me>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Bump the Python runtime used across the project from 3.9 to 3.11. This is a
pure runtime bump: no library versions are changed and the existing Pydantic v1
code keeps working on 3.11.
Changes
backend/Dockerfilepython:3.9-slim-bookworm→python:3.11-slim-bookwormbackend/python/uv.shuv venvpython3.9→3.11backend/python/pydevlake/pyproject.tomlpython = "~3.9"→">=3.11,<3.12"backend/python/plugins/azuredevops/pyproject.tomlpython = "~3.9"→">=3.11,<3.12"backend/python/test/fakeplugin/pyproject.tomlpython = "~3.9"→">=3.11,<3.12".devcontainer/devcontainer.json3.9→3.11backend/python/DevelopmentSetup.mdpython3.11Explicitly out of scope
sqlmodel,pydantic,pytest,inflect,fire,jsonpointeretc. stay unchanged. Pydantic v2 / SQLModel migration and thecorresponding
poetry.lockregeneration are handled in a follow-up PR to keepthis change reviewable and independently revertable.
18).Testing
Automated (on Python 3.11.15):
make build-pydevlake✅ (resolves withpydantic 1.10.26,sqlmodel 0.0.8)make unit-test-python✅ (azuredevops: 8 passed / 1 skipped, pydevlake: 10 passed)Manual:
basestage frombackend/Dockerfile→ image reportsPython 3.11.15, Python remote plugins build successfully.plugin-infoRPChandshake payload (name, extension, 12 subtasks, 14 migration scripts) on 3.11.
Known unrelated issue
devcontainer buildcurrently fails to pullmcr.microsoft.com/devcontainers/go:1-1.26-bookworm(
.devcontainer/Dockerfile). This base-image reference is not touched by this PRand fails identically on
main; it is independent of the Python 3.11 change.Rollback
Revert this single commit; it only changes version strings and has no schema or data impact.