Readthedocs uses Sphinx 3.1.0 and experimental functions and classes show incorrect signature
See original GitHub issueExample
Log on Readthedocs
https://readthedocs.org/projects/optuna/builds/11227856/
How to fix
Fix docs/requirements.txt
should solve this issue.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Sphinx Documentation - Read the Docs
First steps to document your project using Sphinx . ... was out of sync with the code itself, since the function signature was...
Read more >Changelog - Sphinx documentation
#10421: autodoc: autodoc_preserve_defaults doesn't work on class methods ... #9908: autodoc: debug message is shown on building document using NewTypes with ...
Read more >Sphinx AutoAPI Documentation - Read the Docs
__foo__ in Python). • show-inheritance: Display a list of base classes below the class signature. • show-inheritance-diagram: Display an ...
Read more >sphinx Changelog - pyup.io
Fix using ``sphinx.ext.autosummary`` with modules containing titles in the ... 8105: autodoc: the signature of class constructor will be shown for decorated
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Verified the second approach works on my forked repo.
Required changes
https://github.com/harupy/optuna/pull/3/files
Documentation build log
https://readthedocs.org/projects/harupy-optuna/builds/11232421/
Generated documentation
https://harupy-optuna.readthedocs.io/en/latest/reference/visualization.html#optuna.visualization.plot_param_importances
@harupy Thank you for your investigation. I didn’t know that Sphinx uses it. I think it’s reasonable to take the second approach that allows us to integrate the document dependencies into
setup.py
.