-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Show inheritance in Documentation #537
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
Conversation
leotrs
left a comment
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.
I agree we should show inheritance. However, what is the change that required updating configuration.rst?
|
|
TBH I kinda hate the way that configuration.rst looks like right now - when I made it it was just a lazy way of automatically documenting all the available flags, though we might want to do something better in the future. Thanks for fixing it for now tho. |
Same here. Agreed. Do you maybe want to open an issue for it? Reformatting |
|
Looks good, thanks! |
|
It kind of already does in that the first three words in the second sentence are precisely "Abstract base class". |
List of Changes
-q[l|m|h|k]#514 introduced some warnings during documentation build (due to a misformattedtestoutputblock). This is also fixed here.Further Comments
The doctest in
configuration.rstis currently not run as part of the pipeline... maybe we should enable this. (Which would require callingmake doctestfrom thedocsdirectory.)Acknowledgement