Skip to content

fix: Force uv to manage python itself#335

Merged
ptsOSL merged 1 commit into
mainfrom
force-uv-to-manage-python-environment
Apr 24, 2026
Merged

fix: Force uv to manage python itself#335
ptsOSL merged 1 commit into
mainfrom
force-uv-to-manage-python-environment

Conversation

@ptsOSL

@ptsOSL ptsOSL commented Apr 24, 2026

Copy link
Copy Markdown
Contributor

By default uv will use a system installed version of python when available. We don't want this as later in the Dockerfile we require /python to exist which it wont if uv has used a system installed version. This will happen if the requested version of python is the same as the default version in the base image.
https://docs.astral.sh/uv/concepts/python-versions/#requiring-or-disabling-managed-python-versions

By default uv will use a system installed version
of python when available. We dont want this.
https://docs.astral.sh/uv/concepts/python-versions/#requiring-or-disabling-managed-python-versions
@ptsOSL ptsOSL changed the title Force uv to manage python itself fix: Force uv to manage python itself Apr 24, 2026
@ptsOSL
ptsOSL merged commit 1dfadc8 into main Apr 24, 2026
7 of 9 checks passed
@coretl
coretl deleted the force-uv-to-manage-python-environment branch July 14, 2026 11:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants