Repository navigation
Add --select-output - #199
Conversation
|
A thought -- is there a risk of overwriting here? If one process is building the Python 3.12 documentation in French, and a HTML builder is started for Python 3.12 in English, then Prudence seems to suggest that we should use a different checkout for the HTML builds? A |
hugovk
left a comment
hugovk
left a comment
There was a problem hiding this comment.
A thought -- is there a risk of overwriting here?
If one process is building the Python 3.12 documentation in French, and a HTML builder is started for Python 3.12 in English, then build/doctrees could become inconsistent with some French doctrees and some English. Worse, the two processes could be running different builders, changing the checked-out state of the repository.
Prudence seems to suggest that we should use a different checkout for the HTML builds?
Yes, that sounds wise.
2 participants
Towards python/docs-community#131
If either of the options to
--select-outputis given, a different lockfile is generated and checked. We also invert some options because in the future both HTML and non-HTML builds will require archiving their files, so we only skip archiving when--quickis passed.If
--select-outputis missing, the current behaviour is retained, so merging this should have no impact on the current process.I believe that running
rsync -a --delete-delay --filter P archives/ <build path> <target path>is harmless on quick builds, so we remove an if/else here.