-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
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
BUG: Handle NA values for ExtensionArrays in Series.count #26836
Conversation
Codecov Report
@@ Coverage Diff @@
## master #26836 +/- ##
=========================================
+ Coverage 90.45% 91.86% +1.4%
=========================================
Files 179 179
Lines 50706 50706
=========================================
+ Hits 45866 46579 +713
+ Misses 4840 4127 -713
Continue to review full report at Codecov.
|
Codecov Report
@@ Coverage Diff @@
## master #26836 +/- ##
==========================================
- Coverage 91.86% 91.86% -0.01%
==========================================
Files 179 180 +1
Lines 50700 50712 +12
==========================================
+ Hits 46576 46586 +10
- Misses 4124 4126 +2
Continue to review full report at Codecov.
|
BaseMethodsTets.test_count seems to only exercise DataFrame.count. Is this
bug Series-only?
…On Thu, Jun 13, 2019 at 2:14 PM pilkibun ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In pandas/tests/extension/decimal/test_decimal.py
<#26836 (comment)>:
> @@ -380,6 +380,16 @@ def test_divmod_array(reverse, expected_div, expected_mod):
tm.assert_extension_array_equal(mod, expected_mod)
+def test_na_count():
hmm. Why doesn't BaseMethodsTests.test_count catch this bug then?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#26836?email_source=notifications&email_token=AAKAOIWZW646MUAEJ4ID543P2KL7VA5CNFSM4HX4UUN2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB3P5ZXQ#discussion_r293536635>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIRSWPFSKZYHCO2JKBDP2KL7VANCNFSM4HX4UUNQ>
.
|
yeah. more generally It shows there might be lots of bugs still present when frame methods should but don't return the same result as column by column application, due to EA changes. |
btw, what's the norm here, force-push or add commits after review? |
Add new commits.
…On Thu, Jun 13, 2019 at 2:38 PM pilkibun ***@***.***> wrote:
btw, what's the norm here, force-push or add commits after review?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#26836?email_source=notifications&email_token=AAKAOIT6S3VAG4O6YH6MEKTP2KO4NA5CNFSM4HX4UUN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXUZ7EY#issuecomment-501850003>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIXU2BCIPD3HRWKBQTDP2KO4NANCNFSM4HX4UUNQ>
.
|
tests pass and I think I addressed all comments. Ready to merge? |
@pilkibun can you make an ExtensionArray section, and move your release note there? |
added |
Thanks! |
git diff upstream/master -u -- "*.py" | flake8 --diff