-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
DOC: Clean-up references to v12 to v14 (both included) #17420
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: Clean-up references to v12 to v14 (both included) #17420
Conversation
Codecov Report
@@ Coverage Diff @@
## master #17420 +/- ##
==========================================
- Coverage 91.15% 91.14% -0.02%
==========================================
Files 163 163
Lines 49581 49581
==========================================
- Hits 45198 45190 -8
- Misses 4383 4391 +8
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #17420 +/- ##
==========================================
- Coverage 91.15% 91.14% -0.02%
==========================================
Files 163 163
Lines 49581 49581
==========================================
- Hits 45198 45189 -9
- Misses 4383 4392 +9
Continue to review full report at Codecov.
|
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.
couple of comments; also maybe in a separate PR we have lots of versionsdded refs in doc strings
doc/source/indexing.rst
Outdated
@@ -1790,7 +1773,7 @@ Evaluation order matters | |||
|
|||
Furthermore, in chained expressions, the order may determine whether a copy is returned or not. | |||
If an expression will set values on a copy of a slice, then a ``SettingWithCopy`` | |||
exception will be raised (this raise/warn behavior is new starting in 0.13.0) | |||
exception will be raised. |
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.
this is only a warning by default (and depends on the value of the option for raise/warn)
@@ -3078,8 +3062,7 @@ any pickled pandas object (or any other pickled object) from file: | |||
|
|||
.. warning:: | |||
|
|||
Several internal refactorings, 0.13 (:ref:`Series Refactoring <whatsnew_0130.refactoring>`), and 0.15 (:ref:`Index Refactoring <whatsnew_0150.refactoring>`), | |||
preserve compatibility with pickles created prior to these versions. However, these must |
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 would actually leave something this warning because this also applies for 0.19 to current
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've looked through the what's new
section and can find some changes in pickling but can't find anything new about incompatibility. Could you guide me to the relevant section?
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.
@jreback , I've made a proposal on this warning text, that is more general in nature.
If you pictured something different, let me know.
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.
generally for pickle you should simply use pd.read_pickle as we can preserve back compat
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.
Ok, I've written it anew
also update link to python.org
79b9f6d
to
8011a02
Compare
yeah you can take the Experimental off. |
doc/source/enhancingperf.rst
Outdated
to a cython function. Instead pass the actual ``ndarray`` using the ``.values`` attribute of the Series. | ||
|
||
Prior to 0.13.0 | ||
So, do not do this: |
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.
maybe:
This will fail because the cython definition is specific to an ndarray
and not the passed Series
See `here <http://pandas.pydata.org/pandas-docs/stable/whatsnew.html#whatsnew-0130-refactoring>`__ | ||
and `here <http://pandas.pydata.org/pandas-docs/stable/whatsnew.html#whatsnew-0150-refactoring>`__ | ||
for some examples of compatibility-breaking changes. See | ||
`this question <http://stackoverflow.com/questions/20444593/pandas-compiled-from-source-default-pickle-behavior-changed>`__ |
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.
this is good.
.. versionadded:: 0.13.0 | ||
|
||
Starting in 0.13.0, pandas is supporting the ``msgpack`` format for | ||
pandas supports the ``msgpack`` format for |
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.
is this just underlyined in the diff?
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.
There no underline here: https://github.com/topper-123/pandas/blob/15e94c4aad7065db86e713e219aed94b6a80d800/doc/source/io.rst. a bit weird, but my guess is that it's ok
Can't see anything stand out locally either.
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.
just a couple of minor comments. ping when ready and green.
ping @jreback |
thanks! |
git diff upstream/master -u -- "*.py" | flake8 --diff
This is a continution of #17375 and cleans up references to old versions of pandas in the documentation.
Somme issues, I'd appreciate input on:
enhancingperf.rst
there is under "Expression Evaluation via :func:~pandas.eval
(Experimental)" and "TheDataFrame.eval
method (Experimental)" a line..versionadded:: 0.13
.In general I think it's a bit weird that something introduced back in 0.13 still is marked as experimental. I've let the versionadded stay for now, to somehow mark that
eval
is quite old even though it is experimental. Are there thoughts whethereval
should still be marked experimental?