Closed mgedmin closed 1 month ago
Actually, applying the latest meta config fixes tox -e docs (but breaks tox -e lint and tox -e release-check), so I'll try to go that route.
tox -e release-check
is happy if I normalize the supported Python versions with check-python-versions --drop 3.7 --add 3.12
, but tox -e lint
wants to reformat half of the codebase and then fails with an error that is hidden by a voluminous diff, leaving the source tree full of uncommitted changes.
I'm not a fan of tox -e lint
making actual changes to actual source files.
To update to the currently supported Python versions meta/config/update-python-support.py
might come handy as it does everything needed in one go.
Okay, I'm confused. I merged the PR, git pulled from github, ran tox p
, and I'm once again seeing the docs failures about intersphinx_mapping. How come?
I'm was sure they were fixed by the meta/config/config-package.py changes, since it ran tox for me, and it wouldn't have committed/pushed if tox had failed. I should've dug deeper.