-
-
Notifications
You must be signed in to change notification settings - Fork 18.4k
TST: dont break ABCPandasArray checks #27014
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
Comments
Can you clarify? The patch is leaking between tests?
…On Sun, Jun 23, 2019 at 9:59 PM jbrockmendel ***@***.***> wrote:
Apparently tests.extension.tests_numpy patches PandasArray._typ so as to
break all isinstance(obj, ABCPandasArray) checks. Learning this in the
process of troubleshooting failing tests is really frustrating. This is a
code smell and should be removed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#27014?email_source=notifications&email_token=AAKAOIUIRVZ7EKIPUUBZLBLP4A2CRA5CNFSM4H22RXC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4G3F5WMQ>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAKAOIUYP2OPEH6KVCEYC4DP4A2CRANCNFSM4H22RXCQ>
.
|
The patch caused a bunch of failures while putting together #27015 (eventually I had to just disable the entire test file). What is the compelling reason to change the behavior for these tests? |
Because we currently don't allow actually storing them, I think (and that hack is then a way to test them being stored) |
So we want to test that if we allow something that we dont allow, then that thing is allowed? |
We want to test that PandasArray correctly implements the EA interface, part of which requires allowing it to be stored in a Series / DataFrame. |
Apparently tests.extension.tests_numpy patches PandasArray._typ so as to break all
isinstance(obj, ABCPandasArray)
checks. Learning this in the process of troubleshooting failing tests is really frustrating. This is a code smell and should be removed.The text was updated successfully, but these errors were encountered: