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

Revert "CI: workaround numpydev bug (#29433)" #29553

Merged
merged 10 commits into from
Nov 25, 2019

Conversation

TomAugspurger
Copy link
Contributor

This reverts commit b4adb71.

Closes #29432

@TomAugspurger
Copy link
Contributor Author

Hmm a few warnings snuck in.

@jorisvandenbossche is fixing some in #29549 .

I won't have time today or tomorrow for the rest. Anyone able to push fixes to my branch?

@jbrockmendel
Copy link
Member

at least some of these look like the result of #29517; ill see what i can do about it

@jbrockmendel
Copy link
Member

pushed a hopeful-fix, will see how it goes

@jreback jreback added the Compat pandas objects compatability with Numpy or Python functions label Nov 12, 2019
@jreback jreback added this to the 1.0 milestone Nov 12, 2019
@jreback
Copy link
Contributor

jreback commented Nov 12, 2019

lgtm. any perf implications? (IOW now we have to catch moar warnings)?

@jbrockmendel
Copy link
Member

any perf implications? (IOW now we have to catch moar warnings)?

It shouldn't be any worse than the previous solution we had in place that did specific dtype checks to prevent the warnings.

@TomAugspurger
Copy link
Contributor Author

I'm not sure we should be filtering the warnings like this. IIUC this may break in the future when NumPy enforces their deprecation.

I don't know enough of the context for https://github.com/pandas-dev/pandas/pull/29517/files, but we don't want the behavior to silently change for the user. If we like the change from NumPy, then we should not filter the warnings. If we don't like it (say because we need more flexible dtype comparison) then I think we need to restore some of the checks in #29517 (again, I haven't read through the changes there in detail).

@jbrockmendel
Copy link
Member

Tom makes a fair point. I'd be OK with reverting #29517 since having this build is clearly more important.

@jreback
Copy link
Contributor

jreback commented Nov 12, 2019

what if we filter on the specific warning, is that better?

@jbrockmendel
Copy link
Member

just pushed a commit that restored the checks that were removed by #29517. I may try to remove them again someday, but getting this build back up is a higher priority

@jreback
Copy link
Contributor

jreback commented Nov 19, 2019

do we need this?

@TomAugspurger
Copy link
Contributor Author

"This" being the commit Brock pushed up in #29553 (comment)? I think so... That at least gets us back to where we were, and gets us testing against numpydev again.

@jreback
Copy link
Contributor

jreback commented Nov 19, 2019

"This" being the commit Brock pushed up in #29553 (comment)? I think so... That at least gets us back to where we were, and gets us testing against numpydev again.

right. i guess if you can rebase this and see

@TomAugspurger
Copy link
Contributor Author

Merged master.

@jbrockmendel
Copy link
Member

this should be good to go?

@jreback jreback merged commit 2e38d4e into pandas-dev:master Nov 25, 2019
@jreback
Copy link
Contributor

jreback commented Nov 25, 2019

thanks @TomAugspurger and @jbrockmendel

maybe open a followup issue to re-remove this at some point if possible?

proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
proost pushed a commit to proost/pandas that referenced this pull request Dec 19, 2019
lithomas1 added a commit to lithomas1/pandas that referenced this pull request Feb 3, 2023
mroeschke pushed a commit that referenced this pull request Feb 6, 2023
* CLN: Partially revert #29553

* fix tests

* Update missing.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Compat pandas objects compatability with Numpy or Python functions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: Numpydev failing
3 participants