docsbuild-scripts
docsbuild-scripts copied to clipboard
python
scripts for building documentation on docs.python.org
https://docs.python.org/dev/_static/documentation_options.js were not purged from the fastly caches when docsbuild script changed /dev/ symlink to point to 3.12 (so the dropdown menu were thinking it was 3.11).
From an idea of @Mariatta, when we generate the HTML only for a new branch, we could generate a static HTML page containing a nice message like: > This PDF...
Looks like `/objects.inv` (intersphinx thing) has not beed invalidated during the 3.10 release.
If https://docs.python.org/3/_static/documentation_options.js is nor purged, the page displays the proper version but the JS tells another one, so the version switcher picks the wrong version, leading to some confusion.
So we can do: /srv/docsbuild/venv/bin/python /srv/docsbuild/scripts/build_docs.py --quick --language en --branch 3.6 3.7 3.8 Instead of: for branch in 3.6 3.7 3.8; do /srv/docsbuild/venv/bin/python /srv/docsbuild/scripts/build_docs.py --quick --language en --branch $branch; done
docsbuild-scripts could manage the /release/ directory too, this directory is currently manually handled by RMs, see [PEP 101](https://www.python.org/dev/peps/pep-0101/).
I ran a quick test on docs.p.o, now that 3.10 doc can be compiled in parallel, for a single build (one language, one version) : HTML only it takes 2mn...
I mean, when a french browser hits `docs.python.org/` it could be redirected to `docs.python.org/fr/` in a clean way. I'm sure some people prefer reading the english version anway, so we...
Actually all CJK{Chinese, Japanese, Korean} PDF are not generated correctly. The Chinese PDF should be fixed with #70 But I'm not sure what to do with Japanese and Korean. `xeCJK`...
Today, 3.5 is typically never built. But translations are indirectly contributing to it so we may still build it, from time to time. An idea is to monitor the repositories...