-
Notifications
You must be signed in to change notification settings - Fork 914
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
Pin to numpy<1.25 and numba<0.58 to avoid errors and deprecation warnings-as-errors. #14156
Conversation
Sorry, |
I don't have a strong opinion about how we resolve this -- maybe a new issue is best. But for now, I don't see a lot of benefit to fixing these warnings until we are ready to migrate cudf to pandas 2. Then it'll be easier to tell what usage is deprecated in cudf and not just what's deprecated in the pandas internals. If you want to figure that out, I'd appreciate help with filing a second issue (my plate is very full for today already). |
I agree, I don't think we should work on this immediately. I just want an issue tracking this so that we don't forget to move the pin when we bump our pandas version. I'll open a stub issue for tracking that we can fill out with more info later. |
Opened #14166 |
/merge |
Description
Closes #14155.
Related: #14160.
(Will newer numpy support be backported to pandas 1.x? edit: no, see below)
Checklist