Docs: cache jupytext conversion and restore incremental html#603
Draft
cvanelteren wants to merge 1 commit intomainfrom
Draft
Docs: cache jupytext conversion and restore incremental html#603cvanelteren wants to merge 1 commit intomainfrom
cvanelteren wants to merge 1 commit intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This adds a small on-disk cache for Jupytext to notebook conversion used by nbsphinx so repeated docs builds do not re-convert unchanged percent-format notebooks. The cache key includes input content, format, and jupytext version, with an opt-out environment variable and configurable cache directory. It also switches the default docs html target back to incremental behavior by using UPLT_DOCS_EXECUTE=auto and removing -E -a. The html-exec target remains the forced full rebuild path. On RTD the same converter hook runs through docs/conf.py; cross-build cache reuse depends on RTD environment persistence, but local repeated builds reliably benefit.