-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
👌 Add warning log for config values that cannot be cached #12203
👌 Add warning log for config values that cannot be cached #12203
Conversation
Co-authored-by: Bénédikt Tran <[email protected]>
The test failures appear to be unrelated to this PR, or perhaps a result of poor test isolation? edit: commented out the test and it is still failing, so seems some side-effect of the latest python release: |
This reverts commit 3ac2e15.
For posterity: python/cpython#115913 |
As a user and/or extension developer, it can be a source of confusion when, on performing a
sphinx-build
on a cached project, an unchanged configuration variable is always marked as changed (which then triggers a full rebuild).This is often due to the variable being an unpicklable value, like a function, which is silently omitted from the cache (i.e. the
environment.pickle
).This PR introduces a specific warning for when a configuration variable is omitted from the cache, allowing users to understand the root of the problem.