-
Notifications
You must be signed in to change notification settings - Fork 6
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
Post: deprecate config files without sphinx or mkdocs configuration #342
Conversation
content/posts/deprecate-config-files-without-sphinx-or-mkdocs-config.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I thought we were also defaulting to Sphinx and find config
even if you didn't even specify the sphinx:
key, right? Will be good to remove that magic.
Yeah, that's also part of the deprecation. |
content/posts/deprecate-config-files-without-sphinx-or-mkdocs-config.md
Outdated
Show resolved
Hide resolved
@humitos we should probably post this this week if we want it to go out before Christmas. |
…s using Sphinx or MkDocs (#11852) - This introduces a breaking change for users overriding the new (undocumented) jobs (create_environment, install, build.html and friends). This is, if they have overridden any of those jobs without explicitly declaring a Sphinx or MkDocs key, we will no longer run the sphinx/mkdocs commands, not their setup. - This hardcodes the dates from readthedocs/website#342 to through an error to users using the configuration file without an explicit sphinx/mkdocs configuration. This allows for users to keep using the new overrides without worrying about sphinx/mkdocs, while giving enough time to old users to migrate their projects to give an explicit path. ### Some notes - We are allowing to use sphinx/mkdocs and probably other keys with build.commands, even if those keys don't affect the build in anything. Not really something that "interrupt" users in any way, but it can be missleading. - A next step should be to not make python required at all, right now we still create a virtual environment. We probably want to create a virtual env only if python was provided in the list of build.tools. ---- - Ref: readthedocs/website#342 - Closes #10637 - Closes #11819 - Closes #11810 - Closes #11216 --------- Co-authored-by: Manuel Kaufmann <[email protected]>
Ref:
conf.py
/mkdocs.yml
from the repository readthedocs.org#10637📚 Documentation preview 📚: https://readthedocs-about--342.org.readthedocs.build/