Skip to content

DOC: Fix various warnings #18083

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

Merged
merged 5 commits into from
Nov 9, 2017
Merged

Conversation

TomAugspurger
Copy link
Contributor

I'm trying to get our doc build cleaned up. Just fixing warnings in this one
(mostly formatting, some references).

Later on I'll figure out why things are slow on sphinx 1.6 and get rid of our hacked numpydoc / ipython directive.

@TomAugspurger TomAugspurger added this to the 0.21.1 milestone Nov 2, 2017
@codecov
Copy link

codecov bot commented Nov 3, 2017

Codecov Report

Merging #18083 into master will decrease coverage by 0.04%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #18083      +/-   ##
==========================================
- Coverage   91.27%   91.23%   -0.05%     
==========================================
  Files         163      163              
  Lines       50120    50120              
==========================================
- Hits        45749    45728      -21     
- Misses       4371     4392      +21
Flag Coverage Δ
#multiple 89.04% <ø> (-0.03%) ⬇️
#single 40.32% <ø> (-0.06%) ⬇️
Impacted Files Coverage Δ
pandas/core/computation/eval.py 97.02% <ø> (ø) ⬆️
pandas/core/frame.py 97.75% <ø> (-0.1%) ⬇️
pandas/core/generic.py 92.42% <ø> (ø) ⬆️
pandas/core/groupby.py 92.04% <ø> (ø) ⬆️
pandas/io/formats/format.py 95.94% <ø> (ø) ⬆️
pandas/core/indexes/period.py 92.68% <ø> (ø) ⬆️
pandas/io/gbq.py 25% <0%> (-58.34%) ⬇️
pandas/plotting/_converter.py 63.38% <0%> (-1.82%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b4375bd...e2dfa58. Read the comment docs.

@codecov
Copy link

codecov bot commented Nov 3, 2017

Codecov Report

Merging #18083 into master will decrease coverage by 0.16%.
The diff coverage is n/a.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #18083      +/-   ##
==========================================
- Coverage   91.42%   91.26%   -0.17%     
==========================================
  Files         163      163              
  Lines       50068    50116      +48     
==========================================
- Hits        45776    45736      -40     
- Misses       4292     4380      +88
Flag Coverage Δ
#multiple 89.07% <ø> (-0.15%) ⬇️
#single 40.31% <ø> (-0.11%) ⬇️
Impacted Files Coverage Δ
pandas/core/computation/eval.py 97.02% <ø> (ø) ⬆️
pandas/io/formats/format.py 95.94% <ø> (-0.08%) ⬇️
pandas/core/indexes/period.py 92.68% <ø> (-0.21%) ⬇️
pandas/core/generic.py 92.42% <ø> (-3.31%) ⬇️
pandas/core/groupby.py 92.02% <ø> (-0.02%) ⬇️
pandas/core/frame.py 97.75% <ø> (-0.15%) ⬇️
pandas/core/config_init.py 98.34% <ø> (ø) ⬆️
pandas/io/gbq.py 25% <0%> (-58.34%) ⬇️
pandas/core/common.py 91.18% <0%> (-1.83%) ⬇️
... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8dac633...c1b25e9. Read the comment docs.

@TomAugspurger
Copy link
Contributor Author

33 warnings in https://travis-ci.org/pandas-dev/pandas/jobs/296582210, making progress :)

@TomAugspurger
Copy link
Contributor Author

Merging this later today I think, my next round of changing removing our vendored numpydoc and ipython sphinx ext will be more invasive.

Copy link
Member

@jorisvandenbossche jorisvandenbossche left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good hunting! :-)

@@ -1917,7 +1927,7 @@ class Timedelta(_Timedelta):
Parameters
----------
value : Timedelta, timedelta, np.timedelta64, string, or integer
unit : string, [D,h,m,s,ms,us,ns]
unit : string, ``[D,h,m,s,ms,us,ns]``
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this one needed to suppress a warning?
I think we typically do not quote possible values in this part of the docstring (if we quote, I would rather quote them as strings to make it clear that is the option)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah... I think that caused a warning, though I can double check.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Turns out it wasn't necessary. I've changed it to be the correct {'ns', 'us', ...} format.

@@ -1703,6 +1703,7 @@ def to_html(self, buf=None, columns=None, col_space=None, header=True,
Character recognized as decimal separator, e.g. ',' in Europe

.. versionadded:: 0.18.0

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this one actually needed? (the blank line)
I always assumed it was not needed (the one before is needed)
(but note I am not against this change, because without it looks a bit strange in the plain text version)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, not sure if the newline was necessary. There were several "unexpected end to block quote" warnings. I can check my logs.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

don't mind this one. As I said, I think the change is also good from "aesthetic" point of view, whether it was actually needed or not to remove a warning

of the box."""
of the box. Valid values are

* left
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jorisvandenbossche Thoughts on this one? The multiline { options... } format was giving warnings (block quotes I think?). I couldn't figure out the correct values in the formatting, so I just made a list.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See numpy/numpydoc#87. In the end I think the conclusion is that using \ is the best way to deal with multi-line type specifications.

On the other hand, if the list becomes too long of all options, I think it is good to not list them all in the type specification (but keep it there to simply 'string') but give more explanation in the description.

I'm trying to get our doc build cleaned up. Just fixing warnings in this one
(mostly formatting, some references).

Section name warnings

Warning from computation.rst

Remove references to invalid index / columns

Various docstring fixups

More warnings

More warnings
@TomAugspurger
Copy link
Contributor Author

Just the clipboard failure (which seems to be failing more regularly now?)

Merging.

@TomAugspurger TomAugspurger merged commit ba231d4 into pandas-dev:master Nov 9, 2017
@TomAugspurger TomAugspurger deleted the sphinx-2 branch November 9, 2017 11:58
watercrossing pushed a commit to watercrossing/pandas that referenced this pull request Nov 10, 2017
* DOC: Fix various warnings

I'm trying to get our doc build cleaned up. Just fixing warnings in this one
(mostly formatting, some references).

Section name warnings

Warning from computation.rst

Remove references to invalid index / columns

Various docstring fixups

More warnings

More warnings

* match NaT doc

* DOC: Remove duplicate sections

* More warnings

* fixup
No-Stream pushed a commit to No-Stream/pandas that referenced this pull request Nov 28, 2017
* DOC: Fix various warnings

I'm trying to get our doc build cleaned up. Just fixing warnings in this one
(mostly formatting, some references).

Section name warnings

Warning from computation.rst

Remove references to invalid index / columns

Various docstring fixups

More warnings

More warnings

* match NaT doc

* DOC: Remove duplicate sections

* More warnings

* fixup
@TomAugspurger
Copy link
Contributor Author

TomAugspurger commented Dec 8, 2017

Not worth the trouble to backport, moving to 0.22.0

@TomAugspurger TomAugspurger modified the milestones: 0.21.1, 0.22.0 Dec 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants