-
-
Notifications
You must be signed in to change notification settings - Fork 18.6k
DOC: use shared_docs for isna/notna & isnull/notnull #17096
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
Hi @jreback, I am a beginner here and want to work on this issue but am not able to find documentation of how to use shared_docs. Can you provide an example where shared_docs have been used? |
@yadunathg : Awesome that you want to work on this? There is no documentation about how to use this, since it is an internal tool, but you can find an example here: Line 82 in 7bef6d8
You can also search for |
I don't know if this is the best place to leave this comment, and apologies if I should put this elsewhere. Wanted to bring attention to the fact that the docs. claim |
|
@gfyoung thanks for the reply. well yes there is a |
@lermana : Ah, yes, that's true. Then we should decide whether to implement it (long-term) or just patch the docs immediately. I think we should aim for the former if possible. |
@gfyoung cool! would def. be a neat feature to have. A related question: for both Happy to submit a PR for the docs. updates if that would be helpful. Just something I was curious about, don't know if it's mentioned elsewhere in the API specification and missed it... this may not be the proper place for this thread. |
Not AFAICT. Go for it then! |
Cool, will do! |
The consequence of using _shared_docs is that the See also section of the references to
which is exactly the same as the See also section of
This issue is also mentioned in #27609. |
#16972
also some templates so that we can have distinctive doc-strings that use isnull in the doc-string for isnull (rather than isna), same for notnull.
The text was updated successfully, but these errors were encountered: