-
-
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
DEPR/CLN: Clean up to_dense signature deprecations #22910
Conversation
Hello @gfyoung! Thanks for submitting the PR.
|
Codecov Report
@@ Coverage Diff @@
## master #22910 +/- ##
==========================================
- Coverage 92.19% 92.18% -0.01%
==========================================
Files 169 169
Lines 50954 50946 -8
==========================================
- Hits 46975 46967 -8
Misses 3979 3979
Continue to review full report at Codecov.
|
hmm, this might need to go in after @TomAugspurger refactor of Sparse (#22325) |
Sounds good. I'll wait until that's done then. |
21de4f4
to
fa36970
Compare
Looks like Azure is failing on |
I'm fine with ignoring these failures for now if the code isn't touching window / pyarrow. |
@TomAugspurger : These changes don't touch either of those. That being said, I'm in no rush to merge these, and I see that you are getting close on #23182. Unless somebody needs these deprecations removed NOW, I think I can hold. |
I think we could deprecate |
Ah, hence the |
i agree we should deprecate get_values fully i tried this a while back and it’s not so easy maybe easier now that SpareArray is here |
"in principle" it should not be used internally (outside of sparse itself), as it is not part of the EA interface (or where it is used in sparse specific code, it should be replacable with to_dense) I think it is certainly worth to check in this PR. |
I didn't follow the sparse refactoring too closely, but to what extent are we trying to have a consistent interface for I ask this because although I'm also inclined to deprecate |
this looks fine. can you rebase to get this passing. ping on green. |
I think we have an issue about deprecating |
@gfyoung yep ok. |
There does not need to be a consistency here, since we are considering deprecating SparseSeries/DataFrame alltogether. I still think it doesn't make sense to only deprecate the keyword if we are actually planning to deprecate the full method. I would directly do that, otherwise you annoy users twice for nothing. |
FYI, I've started a exploring a deprecation for SparseDataFrame /
SparseSeries. I think it'll be doable for 0.24.
…On Wed, Oct 17, 2018 at 7:04 AM Joris Van den Bossche < ***@***.***> wrote:
to what extent are we trying to have a consistent interface for
SparseArray with respect to SparseSeries and SparseDataFrame ?
There does not need to be a consistency here, since we are considering
deprecating SparseSeries/DataFrame alltogether.
I still think it doesn't make sense to only deprecate the feature if we
are actually planning to deprecate the full method. I would directly do
that, otherwise you annoy users twice for nothing.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22910 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABQHIuZgUn9b-20IRUSOIMMwCg4Xz1oKks5ulxzegaJpZM4XBGN8>
.
|
As @jreback had warned beforehand, there are unfortunately still some issues with trying to deprecate |
I think it was about But, can you give a bit more details about the issues you encountered? That's useful information to keep track of. |
@jorisvandenbossche : There were some errors in the sparse index testing. I'll try to debug as a follow-up. |
fa36970
to
2d1cebf
Compare
@jreback : Addressed all comments, and all is green again! PTAL. |
@gfyoung was looking at the diff now, and was wondering: can't you simply remove the |
@jorisvandenbossche : Ah! That's a good point! Let me do that then (given the warning message was not specific to either method). |
Also deprecate `fill` in `.get_values` because its parameter was being passed to `.to_dense`, which no longer accepts the `fill` parameter. xref pandas-devgh-14686.
624568a
to
bfbae5c
Compare
@jreback @jorisvandenbossche : Comments addressed, and all is green! PTAL. |
thanks @gfyoung |
Also deprecate `fill` in `.get_values` because its parameter was being passed to `.to_dense`, which no longer accepts the `fill` parameter. xref pandas-devgh-14686.
Also deprecate
fill
in.get_values
because its parameter was being passed to.to_dense
, whichno longer accepts the
fill
parameter.xref #14686.