Discovered during work in #589:
The CI uses Python 3.12 and things all work.
However, the CI success is just luck. The docs do not build with Python >= 3.13. To reproduce this, compare the outputs of:
uv python install 3.13
uv sync -p 3.13 --all-groups
uv run make -C docs
(rm -rf .venv now to make things clean.)
uv python install 3.12
uv sync -p 3.12 --all-gropus
uv run make -C docs
Only the latter works. I discovered this because I have 3.13 and 3.14 installed on Fedora and was running into problems.
The practical implication is that changes to the developer docs in #589 likely will not work for people (who probably have >= 3.13 on their systems). But we should not change the docs. Rather, we should make sure that a valid development environment can happen on the current Python release. We should also do this before the next release?
Ultimately, fixing this requires bumping the version numbers pinned for jupyter-book.
I have already experimented with this and demes-spec also needs updating re: this dependency.
Discovered during work in #589:
The CI uses Python 3.12 and things all work.
However, the CI success is just luck. The docs do not build with Python >= 3.13. To reproduce this, compare the outputs of:
(
rm -rf .venvnow to make things clean.)Only the latter works. I discovered this because I have 3.13 and 3.14 installed on Fedora and was running into problems.
The practical implication is that changes to the developer docs in #589 likely will not work for people (who probably have >= 3.13 on their systems). But we should not change the docs. Rather, we should make sure that a valid development environment can happen on the current Python release. We should also do this before the next release?
Ultimately, fixing this requires bumping the version numbers pinned for jupyter-book.
I have already experimented with this and demes-spec also needs updating re: this dependency.