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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
apt
python3-sphinxinstalls for wrong Python versionLow Severity
With the base image change from
python:3.9.15(Debian Bullseye, system Python 3.9) topython:3.13.12(Debian Bookworm, system Python 3.11), theapt-get install python3-sphinxnow installs Sphinx for system Python 3.11 rather than the container's primary Python 3.13. This makes the apt-installed Sphinx package effectively useless — project packages fromuv syncare installed for Python 3.13, so the apt-installedsphinx-build(using Python 3.11) cannot access them. Thebuild_docs.shscript works around this by pip-installing sphinx extensions (which pulls in Sphinx for Python 3.13), but the apt package now adds unnecessary bloat and a potentially confusing second Python installation.