- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
autodoc_default_flags
deprecated on a minor version
#5421
Labels
Milestone
Comments
vrde
added a commit
to vrde/bigchaindb
that referenced
this issue
Sep 13, 2018
Solution: Move from `autodoc_default_flags` to `autodoc_default_options`. Related issue: - sphinx-doc/sphinx#5421
ttmc
pushed a commit
to bigchaindb/bigchaindb
that referenced
this issue
Sep 13, 2018
Solution: Move from `autodoc_default_flags` to `autodoc_default_options`. Related issue: - sphinx-doc/sphinx#5421
Thank you for reporting. We've not adopted to semantic versioning yet. But this warning has not obey to our deprecation rule. I marked this as a bug and will fix this later. |
tk0miya
added a commit
to tk0miya/sphinx
that referenced
this issue
Sep 13, 2018
…autodoc_default_flags`
tk0miya
added a commit
that referenced
this issue
Sep 14, 2018
…t_flags Fix #5421: autodoc emits deprecation warning for :confval:`autodoc_default_flags`
Fixed by #5424. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Disclaimer: I assume Sphinx follows the Semantic Versioning rules.
Subject: Sphinx 1.8 is not backward compatible since it deprecates
autodoc_default_flags
.Problem
sphinx/CHANGES
Line 149 in efdc95e
Procedure to reproduce the problem
I'll skip this section, if you need the commands I can add them later.
Error logs / results
Expected results
If Sphinx follows the Semantic Versioning rules, it shouldn't error out if
autodoc_default_flags
is used. Removing the option is a breaking change and should happen in the next major version of Sphinx (2.0?).Reproducible project / your project
Environment info
The text was updated successfully, but these errors were encountered: