-
Notifications
You must be signed in to change notification settings - Fork 1.1k
DOC: fix napoleon, render sphinx docs right #691
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
DOC: fix napoleon, render sphinx docs right #691
Conversation
Thanks Mark. My understanding is that we should use either the |
new docs as rendered are here |
Overall, I prefer the napoleon formatting. I also like that it links to the allowed types. I wonder if there's a way to link to custom definitions for "numeric" and "array-like" (not required here, just thinking). I've listed a handful of issues below. Many of these are also issues in the numpydoc build, but the differences in formatting have made them breaking issues instead of nice to have fixes.
Things that are entirely broken in both and not required here: |
|
ah, I prefer the behavior when set to |
It appears that the
|
napolean directives I did not use:
|
* set napoleon_use_rtype = False - for nicer style, combines return type in parentheses after return name * in bifacial use Parameters instead of Inputs * in location use add newline and tab after kwargs parameter in two places * in model chain remove return and separate Notes * in solarposition, add newline and tab after return type * in tracking add Parameters to docstring for SingleAxisTracker
Make sure to reset browser cache before checking rendered docs |
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 like it! Minor comments and line too long errors...
* remove from - INSTALL REQUIRES in setup.py - extensions in conf.py, also remove numpydoc directive - tutorials environment yml * fix typo for singleaxis in tracking.py * stickler CI - too long lines in tracking.py and modelchain.py * fix some formatting, confusing markdown and rst code backticks Signed-off-by: Mark Mikofski <[email protected]>
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.
Thanks Mark!
pvlib python pull request guidelines
Thank you for your contribution to pvlib python! You may delete all of these instructions except for the list below.
You may submit a pull request with your code at any stage of completion.
The following items must be addressed before the code can be merged. Please don't hesitate to ask for help if you're unsure of how to accomplish any of the items below:
docs/sphinx/source/api.rst
for API changes.docs/sphinx/source/whatsnew
file for all changes.Brief description of the problem and proposed solution (if not already fully described in the issue linked to above):
conf.py
solar_zenith_analytical