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

Deprecate Series/Dataframe.to_dense/to_sparse #26668

Closed
wants to merge 4 commits into from
Closed

Deprecate Series/Dataframe.to_dense/to_sparse #26668

wants to merge 4 commits into from

Conversation

VikramjeetD
Copy link
Contributor

@VikramjeetD VikramjeetD commented Jun 5, 2019

Marks the methods mentioned in #26557 as deprecated, with proper messages.

@pep8speaks
Copy link

pep8speaks commented Jun 5, 2019

Hello @intell1gent! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2019-06-05 16:21:20 UTC

@codecov
Copy link

codecov bot commented Jun 5, 2019

Codecov Report

Merging #26668 into master will decrease coverage by 50.09%.
The diff coverage is 50%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26668      +/-   ##
==========================================
- Coverage   91.87%   41.78%   -50.1%     
==========================================
  Files         174      174              
  Lines       50663    50671       +8     
==========================================
- Hits        46548    21172   -25376     
- Misses       4115    29499   +25384
Flag Coverage Δ
#multiple ?
#single 41.78% <50%> (-0.06%) ⬇️
Impacted Files Coverage Δ
pandas/core/sparse/frame.py 28.37% <0%> (-67.26%) ⬇️
pandas/core/sparse/series.py 44.49% <0%> (-50.42%) ⬇️
pandas/core/frame.py 35.07% <100%> (-62.05%) ⬇️
pandas/core/series.py 45.42% <100%> (-48.19%) ⬇️
pandas/io/formats/latex.py 0% <0%> (-100%) ⬇️
pandas/io/sas/sas_constants.py 0% <0%> (-100%) ⬇️
pandas/core/groupby/categorical.py 0% <0%> (-100%) ⬇️
pandas/tseries/plotting.py 0% <0%> (-100%) ⬇️
pandas/tseries/converter.py 0% <0%> (-100%) ⬇️
pandas/io/formats/html.py 0% <0%> (-99.37%) ⬇️
... and 132 more

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 e0c41f7...39230d4. Read the comment docs.

@codecov
Copy link

codecov bot commented Jun 5, 2019

Codecov Report

Merging #26668 into master will decrease coverage by <.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master   #26668      +/-   ##
==========================================
- Coverage   91.87%   91.87%   -0.01%     
==========================================
  Files         174      174              
  Lines       50663    50669       +6     
==========================================
+ Hits        46548    46550       +2     
- Misses       4115     4119       +4
Flag Coverage Δ
#multiple 90.4% <100%> (ø) ⬆️
#single 41.75% <50%> (-0.09%) ⬇️
Impacted Files Coverage Δ
pandas/core/sparse/frame.py 95.65% <100%> (+0.01%) ⬆️
pandas/core/frame.py 97% <100%> (-0.12%) ⬇️
pandas/core/series.py 93.62% <100%> (ø) ⬆️
pandas/core/sparse/series.py 94.93% <100%> (+0.02%) ⬆️
pandas/io/gbq.py 78.94% <0%> (-10.53%) ⬇️

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 e0c41f7...39230d4. Read the comment docs.

@VikramjeetD VikramjeetD closed this Jun 5, 2019
@VikramjeetD VikramjeetD reopened this Jun 5, 2019
@VikramjeetD VikramjeetD closed this Jun 5, 2019
@jorisvandenbossche
Copy link
Member

@intell1gent is there a reason you closed this?

@VikramjeetD
Copy link
Contributor Author

@intell1gent is there a reason you closed this?

@jorisvandenbossche Sorry, there was some confusion on my side. Opened a new PR ( #26684 ) since this has become a bit messy.

@jorisvandenbossche
Copy link
Member

@intell1gent OK, will look at the other PR. Just a feedback for in the future: in general you don't need to make new PRs if something has become messy. If you clean up the branch locally and push again, the PR gets updated automatically.
Also, it is always recommended to work from a different branch than 'master' for a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

DEPR: deprecate Series/DataFrame.to_dense/to_sparse
3 participants