Skip to content
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 validation of the section order in docstrings #23607

Merged
merged 2 commits into from
Nov 12, 2018
Merged

DOC: Adding validation of the section order in docstrings #23607

merged 2 commits into from
Nov 12, 2018

Conversation

datapythonista
Copy link
Member

@datapythonista datapythonista added Docs CI Continuous Integration labels Nov 9, 2018
@pep8speaks
Copy link

Hello @datapythonista! Thanks for submitting the PR.

@codecov
Copy link

codecov bot commented Nov 9, 2018

Codecov Report

Merging #23607 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master   #23607   +/-   ##
=======================================
  Coverage   92.25%   92.25%           
=======================================
  Files         161      161           
  Lines       51260    51260           
=======================================
  Hits        47290    47290           
  Misses       3970     3970
Flag Coverage Δ
#multiple 90.63% <ø> (ø) ⬆️
#single 42.33% <ø> (ø) ⬆️

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 9179e63...df5c1bc. Read the comment docs.

@jreback jreback added this to the 0.24.0 milestone Nov 11, 2018
@jreback
Copy link
Contributor

jreback commented Nov 11, 2018

lgtm. @jorisvandenbossche @TomAugspurger

@datapythonista
Copy link
Member Author

@TomAugspurger do you mind having a quick look here, and merge if you're happy? I'd like to create the issue to fix the wrong section names.

('Found unknown section "Unknown Section".',)),
('BadGenericDocStrings', 'sections_in_wrong_order',
('Wrong order of sections. "See Also" should be located before '
'"Notes"',)),
Copy link
Contributor

Choose a reason for hiding this comment

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

To make sure I understand the error message, we say "See Also should be located before Notes" because it's the section immediately preceding notes. But the "users" docstring in this case doesn't have a "Notes" section, so that's slightly confusing.

I was hoping we could instead say "See Also should be located before Examples", but that's not quite right either, because if you have three out of order sections, you would want to skip back two sections, if that makes sense...

So I guess my only comment is, "this error message is potentially confusing. But I don't know how to improve it". If you see an easy way to improve it, push it here. Otherwise +1 from me.

Copy link
Member Author

Choose a reason for hiding this comment

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

Good point, I 100% agree. I couldn't find a better way to report it, without dong something too complex and possibly even more misleading.

But I think it should be all right, as in the error message I show the order of all sections (is not shown in the test, but will be displayed to the users).

May be after this starts to be used someone comes with a better idea. But I think it should be good enough.

Copy link
Contributor

Choose a reason for hiding this comment

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

But I think it should be all right, as in the error message I show the order of all sections (is not shown in the test, but will be displayed to the users).

Ah great. That sounds fine.

@TomAugspurger TomAugspurger merged commit b9ba708 into pandas-dev:master Nov 12, 2018
thoo added a commit to thoo/pandas that referenced this pull request Nov 12, 2018
…fixed

* upstream/master:
  DOC: avoid SparseArray.take error (pandas-dev#23637)
  CLN: remove incorrect usages of com.AbstractMethodError (pandas-dev#23625)
  DOC: Adding validation of the section order in docstrings (pandas-dev#23607)
  BUG: Don't over-optimize memory with jagged CSV (pandas-dev#23527)
  DEPR: Deprecate usecols as int in read_excel (pandas-dev#23635)
  More helpful Stata string length error. (pandas-dev#23629)
  BUG: astype fill_value for SparseArray.astype (pandas-dev#23547)
  CLN: datetimelike arrays: isort, small reorg (pandas-dev#23587)
  CI: Check in the CI that assert_raises_regex is not being used (pandas-dev#23627)
  CLN:Remove unused **kwargs from user facing methods (pandas-dev#23249)
JustinZhengBC pushed a commit to JustinZhengBC/pandas that referenced this pull request Nov 14, 2018
…#23607)

* Adding validation of the section order in docstrings

* Updating allowed sections
tm9k1 pushed a commit to tm9k1/pandas that referenced this pull request Nov 19, 2018
…#23607)

* Adding validation of the section order in docstrings

* Updating allowed sections
Pingviinituutti pushed a commit to Pingviinituutti/pandas that referenced this pull request Feb 28, 2019
…#23607)

* Adding validation of the section order in docstrings

* Updating allowed sections
Pingviinituutti pushed a commit to Pingviinituutti/pandas that referenced this pull request Feb 28, 2019
…#23607)

* Adding validation of the section order in docstrings

* Updating allowed sections
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CI Continuous Integration Docs
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DOC: Validate the order of the sections in the docstrings
4 participants