-
-
Notifications
You must be signed in to change notification settings - Fork 18.1k
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: Fixing even more warnings (not many left) #26850
DOC: Fixing even more warnings (not many left) #26850
Conversation
Codecov Report
@@ Coverage Diff @@
## master #26850 +/- ##
==========================================
- Coverage 91.86% 91.85% -0.01%
==========================================
Files 179 179
Lines 50700 50700
==========================================
- Hits 46576 46572 -4
- Misses 4124 4128 +4
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #26850 +/- ##
===========================================
- Coverage 91.86% 41.08% -50.79%
===========================================
Files 179 179
Lines 50700 50717 +17
===========================================
- Hits 46576 20835 -25741
- Misses 4124 29882 +25758
Continue to review full report at Codecov.
|
Almost! ;) There are two left (from the ones we could solve): /home/travis/build/pandas-dev/pandas/doc/source/reference/api/pandas.Index.asi8.rst: WARNING: document isn't included in any toctree About the ExtensionDtype.na_value: It doesn't seem generated in the actual class docstring page (http://dev.pandas.io/reference/api/pandas.api.extensions.ExtensionDtype.html#pandas.api.extensions.ExtensionDtype), so I think we can remove the comment at the bottom of https://raw.githubusercontent.com/pandas-dev/pandas/master/doc/source/reference/index.rst to avoid the warning |
Didn't see where Feel free to look at those if you want, and also:
I think we should be able to start failing on warnings today, before more are introduced. :) |
I made the change locally, will push here |
… page to link to)
I just saw that the virtualenv error doesn't happen in azure, there are just 3 warnings left there according to sphinx. Better don't bother then, it's in azure where we need to add the validation. |
Do you already know how you would do the validation? Can we capture and parse the log build in azure? |
sphinx has parameters for that:
|
I think we had some discussion about that before, but some problems with that: a) it doesn't handle the ipython directive errors (I think?) and b) it doesn't allow us to have some exceptions (eg to ignore our contributor directive that needs the full git history) |
…ocstring page to link to)" This reverts commit ba2b6ce.
Hmm, my commit didn't work, reverting. |
Let's already merge those. |
git diff upstream/master -u -- "*.py" | flake8 --diff
Let's wait for the logs, tested locally only part of them, but this should fix most of the remaining warnings.
CC: @jorisvandenbossche