-
Notifications
You must be signed in to change notification settings - Fork 171
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] Adding minimal working examples to docstrings; a checklist #972
Comments
I'm currently having a look at
Will probably look at some more as and when I have time over the next week or so |
This is awesome, @thatlittleboy! Thank you for handling this here 😄. I've invited you to the dev team to help move this along. |
One trick I'm finding is that it's pretty easy to create a minimal working example from the test suite 😹. |
Ongoing sprint, dibs on the following:
|
Same here, dibs on:
|
Dibs on:
Two per PR seems to be the load that I personally can handle 😹. |
Ongoing sprint:
|
Going to work on:
|
Ongoing sprint:
|
Ongoing sprint:
|
Currently looking at:
Also in the midst of updating:
|
Pycon 2022 - working on timeseries.py |
I'll also do |
I'll do functions/fill.py |
Pycon 2022 - working on |
Pycon 2022 - working on |
I'll do |
Dibs on |
For my next trick, I'd like to do biology.py |
It looks like Dibs on |
* include gcc in container * Doctests in chemistry.py docstrings - #972 Co-authored-by: Catherine Devlin <[email protected]>
Dibs on finance.py |
I'll do |
I'll do |
* include gcc in container * doc-972-doctests-in-biology Co-authored-by: Catherine Devlin <[email protected]>
Background
This thread is borne out of the discussion from #968 , in an effort to make documentation more beginner-friendly & more understandable.
One of the subtasks mentioned in that thread was to go through the function docstrings and include a minimal working example to each of the public functions in pyjanitor.
Criteria reiterated here for the benefit of discussion:
Sample of what MWE should look like is shown here.
I'm thinking we can create a task list so that 1. we can encourage more users to join in the effort, and 2. make sure we don't do duplicate work. A lot of the groundwork can be covered by selectively copying one or two examples over from the software test suite.
Then we can label this issue as a Help Wanted / Low-Hanging Fruit and get people to mention in this thread if they're intending to work on the files?
Task list
B
The text was updated successfully, but these errors were encountered: