-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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: api.py, docstring improvements #7732
Conversation
This pull request introduces 10 alerts when merging 0408b6f into 2e07422 - view on LGTM.com new alerts:
|
Cleanup of module namespaces didn't work (I thought I had done this in the (distant) past) In my notebook I only imported the modules to check available names. I didn't run any functions. That works without problems. (initially posted to wrong issue) |
checking module name finds imports, e.g.
but has false positives, if a function is written in another module, but the current module is the "official" public module for it. |
0408b6f
to
ce21816
Compare
I removed all the I still have a few functions missing in api.py for which I'm not sure about whether or how to add them, e.g. knockoff_effects and outlier_influence |
related aside: |
This pull request introduces 10 alerts when merging ce21816 into 2e07422 - view on LGTM.com new alerts:
|
ce21816
to
c89bcda
Compare
merge when green I will do another round later |
|
I think you need to link to the actual location that is used in the docs, not the API version. |
Also see
Is notebook working correctly? |
This pull request introduces 12 alerts when merging c89bcda into 20082ce - view on LGTM.com new alerts:
|
something strange |
Import error, I made a mistake and didn't run the |
Can you add an |
problem/type with singular or plural names, I might have to rename a module |
why does LGTM ignore pylint and flake options in module?
which satisfies the azure style check in copulas.api |
Why not just add to |
because it's a pain to maintain and it is never used. |
It is used by ipython.
…On Tue, Sep 21, 2021, 17:13 Josef Perktold ***@***.***> wrote:
Why not just add to *all* which is the correct approach?
because it's a pain to maintain and it is never used.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7732 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKTSRO5YS3NPBHNJT2BTYTUDCVL5ANCNFSM5EMROAXQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
c89bcda
to
bf946d3
Compare
This pull request introduces 3 alerts when merging bf946d3 into 20082ce - view on LGTM.com new alerts:
|
another false alarm in docs: the links to the two other notebooks work correctly in the
I have one mistake in api.rst, wrong path to model |
bf946d3
to
6f18ef0
Compare
This pull request fixes 8 alerts when merging 6f18ef0 into 20082ce - view on LGTM.com fixed alerts:
|
more docstrings #7564
and api cleanup in stats #7013
The two issues are not finished by this PR, still some problems left
this includes now some additions to api.rst, and some reordering init by topic