-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
Numpydoc for backends #7397
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
Numpydoc for backends #7397
Conversation
I've added types to all the backend files I've already touched. The descriptions are not perfect, but several of the backends do not appear in the documentation, presumably because they cannot all be loaded at the same time or the dependencies are not available. I tried adding them, but it broke the builds, so that's something for another time. |
|
||
* `interval`: The time between timer events in | ||
milliseconds. Default is 1000 ms. | ||
single_shot: bool |
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.
Here and below, my understanding from @NelleV is that the colon must be surrounded by spaces.
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.
Grrr, thought I got all of those.
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.
Yep, else it won't render properly. I wouldn't hold this PR for this thought. It's been around way too long.
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 fine based on a quick scan, apart from the two spots where spaces probably need to be inserted.
The previous changes were intended for napoleon, but that has yet to be merged. NumPyDoc supports a few less section names, and requires them to be in a specific order. Also, a little bit of whitespace change needed to render stuff properly.
e3c61c1
to
cff8615
Compare
Huh, that was way more outdated than I thought, but fortunately no conflicts. Rebased and addressed the last two comments. |
I've had this lying around for a while, but it's incomplete insofar as I didn't have a chance to add types to everything. I don't really want it to go completely to waste though.
Apparently, I had a lot of free time at the beginning of the year and did the same for a lot of other files. The trouble is, that was with the expectation of switching to napoleon, so there are a few corrections that need to be made to work with our current build (which you can see in the second commit here.) Should I post those up somewhere (and maybe tag with Need contributor)?