Filter warning in sparse repr

[TomAugspurger]

xref #26555

[codecov]

Codecov Report

Merging #26669 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #26669      +/-   ##
==========================================
- Coverage   91.87%   91.86%   -0.01%     
==========================================
  Files         174      174              
  Lines       50663    50663              
==========================================
- Hits        46548    46544       -4     
- Misses       4115     4119       +4

Flag	Coverage Δ
#multiple	90.4% <ø> (ø)	⬆️
#single	41.78% <ø> (-0.06%)	⬇️

Impacted Files	Coverage Δ
pandas/core/sparse/frame.py	95.63% <ø> (ø)	⬆️
pandas/core/sparse/series.py	94.9% <ø> (ø)	⬆️
pandas/io/gbq.py	78.94% <0%> (-10.53%)	⬇️
pandas/core/frame.py	97% <0%> (-0.12%)	⬇️

---

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...79e2705. Read the comment docs.

[jreback]

lgtm.

[jreback]

this should close #26555 yes? (or is there more to do?)

[TomAugspurger]

Still more to do in theory. Things like SparseDataFrame + SparseDataFrame will still emit warnings since we create intermediate SparseSeries. I probably won't put more time into sparse though.

…

On Wed, Jun 5, 2019 at 4:40 PM Jeff Reback ***@***.***> wrote: this should close #26555 <#26555> yes? (or is there more to do?) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#26669?email_source=notifications&email_token=AAKAOIR2UD77XBAVRVZBACDPZAXDXA5CNFSM4HUALGJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXBDBWI#issuecomment-499265753>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAKAOIV2XML2E4MRYGWVASLPZAXDXANCNFSM4HUALGJQ> .

[jreback]

ok thanks, good for now then