-
Notifications
You must be signed in to change notification settings - Fork 284
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
Usage deprecated in pandas 0.23 #3018
Comments
We have talked very recently of deprecating this module. It won't solve our issue (as we still need to find a solution), but it may prevent this occurring in the future... |
Apologies for butting in. Isn't the answer here to use (and check for) df.values.base instead of df.base, which would, I think, work with both older versions and 0.23? As for deprecating this module, while I have used it for using iris with UGRID data, it's a bit of a niche usage so I'm not sure I could make a compelling case against deprecation. |
@hdyson - I'm not close enough to the pandas API to answer definitively, but that suggestion sounds sensible. Would be happy to merge if you want to submit a PR? |
@pelson A couple of quick questions here. Has there been a resolution to the conversation about deprecating the cube to/from dataframe/series functionality? And if it is to be deprecated, will this functionality leave iris before the switch over to a pandas version which will have an error rather than a deprecation warning? For the fix itself, I'd be happy to provide it; I'm just trying to confirm we're not in "re-arranging deckchairs on the Titanic" territory. |
Lol. Love the metaphor! No decision has been made really. It seems like one
of those corners of Iris that doesn't get any attention, and is therefore
ripe for consideration to be deprecated. No matter what though, code won't
be deleted until v3.
…On Mon, 11 Jun 2018, 12:20 hdyson, ***@***.***> wrote:
@pelson <https://github.com/pelson> A couple of quick questions here. Has
there been a resolution to the conversation about deprecating the cube
to/from dataframe/series functionality? And if it is to be deprecated, will
this functionality leave iris before the switch over to a pandas version
which will have an error rather than a deprecation warning?
For the fix itself, I'd be happy to provide it; I'm just trying to confirm
we're not in "re-arranging deckchairs on the Titanic" territory.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3018 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAxep-6pYZ6QlhVlOjk8pM5apSnXcsZsks5t7lKSgaJpZM4UBhTb>
.
|
Looks like this was fixed by #3079. |
There was initially a failure due to pandas 0.22 -> 0.23 in #3017,
fixed by a tiny tweak.
However there is an outstanding deprecation warning emerging from the tests ..
That arises from the code here
This is not so trivial a problem :
as existing code indicates, the usage of the 'base' property already changed.
If I understand right, potentially we can now just replace 'base' with 'values'.
- except that would no longer work with older versions of pandas.
However, right now, even testing for the presence of a '.base' attribute is triggering the deprecation warning.
The text was updated successfully, but these errors were encountered: