-
-
Notifications
You must be signed in to change notification settings - Fork 17.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: Adding offsets to API ref #24446
Conversation
Is it possible to give |
Totally agree, but I think the short answer is no. I copied the format of: https://pandas-docs.github.io/pandas-docs-travis/api.html#scalars IMO, what we should do is split the API page in several sections (see the sections in the "API Reference" block in https://pandas-dev.github.io/pandas-sphinx-theme/pr-datapythonista_base/, but possibly with all Index classes in the same section). Then we should have at least one extra level of title/subtitle..., and we'll be able to do it. Will open an issue soon, and see if there is agreement. |
it didn’t have clickable links before |
ah, I see, thanks for clarifying. But that's somehow unrelated, the class pages already existed, it's just that they are not links. I'll add those in a separate PR. |
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
5 similar comments
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #24446 +/- ##
=======================================
Coverage 92.3% 92.3%
=======================================
Files 163 163
Lines 51977 51977
=======================================
Hits 47979 47979
Misses 3998 3998
Continue to review full report at Codecov.
|
Created #24448 for the links. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you auto-generate these?
|
||
DateOffset.apply | ||
DateOffset.copy | ||
DateOffset.isAnchored |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we are removing / not-advertising isAnchored
DateOffset.freqstr | ||
DateOffset.kwds | ||
DateOffset.name | ||
DateOffset.nanos |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we consider .nanos private @jbrockmendel ?
I "autogenerated" them, would you prefer to generate the content of Regarding the private methods, sphinx will warn (and eventually we'll make it fail for warnings). So it'd probably be a better option to just rename them to Related to this PR, I created #24451 to split |
this is fine for now (and ok on the splitting). |
* upstream/master: (26 commits) DOC: Fixing doc upload (no such remote origin) (pandas-dev#24459) BLD: for C extension builds on mac, target macOS 10.9 where possible (pandas-dev#24274) POC: _eadata (pandas-dev#24394) DOC: Correct location (pandas-dev#24456) CI: Moving CircleCI build to Travis (pandas-dev#24449) BUG: Infer compression by default in read_fwf() (pandas-dev#22200) DOC: Fix minor typo in whatsnew (pandas-dev#24453) DOC: Add dateutil to intersphinx pandas-dev#24437 (pandas-dev#24443) DOC: Adding links to offset classes in timeseries.rst (pandas-dev#24448) DOC: Adding offsets to API ref (pandas-dev#24446) DOC: fix flake8 issue in groupby.rst (pandas-dev#24363) DOC: Fixing more doc warnings (pandas-dev#24438) API: Simplify repeat signature (pandas-dev#24447) BUG: to_datetime(Timestamp, utc=True) localizes to UTC (pandas-dev#24441) CLN: Cython Py2/3 Compatible Imports (pandas-dev#23940) DOC: Fixing more doc warnings (pandas-dev#24431) DOC: Removing old release.rst (pandas-dev#24427) BUG-24408 Series.dt does not maintain own copy of index (pandas-dev#24426) DOC: Fixing several doc warnings (pandas-dev#24430) ENH: fill_value argument for shift pandas-dev#15486 (pandas-dev#24128) ...
Adding Date Offsets API documentation. Added in the same format as other sections. Detected what are properties and what are methods with the
callable
function. The order of the classes is the one already used. The order inside properties and methods is alphabetical.@jreback In
timeseries.rst
we already have a table with the different offsets: https://pandas-docs.github.io/pandas-docs-travis/timeseries.html#dateoffset-objects Not sure what would you like to add more.This is how it looks like:
CC: @mroeschke @jbrockmendel