-
-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
Numpy version incompatibility #32056
Comments
You'll need to provide more information on how you installed NumPy and pandas. |
I was previously using pandas 0.25.1 I believe, along with numpy 1.15.4 The issue appeared when upgrading to pandas with |
Did you build from source or install wheels? Ideally you could provide the full inputs and outputs of a terminal session. |
I'm pretty sure ive seen this on either the cython tracker or mailing list |
Hi again, I believe this is what you're asking for:
Also, seems like pandas was installed from wheels.
|
I might naively expect the following to work
assuming that pandas was built against NumPy 1.13.3 as specified in https://github.com/pandas-dev/pandas/blob/master/pyproject.toml#L8-L9 (for Python 3.6) @cgohlke do you know what version of NumPy pandas 1.0.1 was compiled with? |
1.14.6 |
I can reproduce the error. Numpy >= 1.16 work. |
@seberg is this a resolved issue? |
I think this is a sanity check in cython, which is being a bit overzealous, and probably is simply fixed in Cython (in the sense that it is now normally a warning, and NumPy actually filters the warning away). I am not sure there is anything we can do about it, it is possible the size of the ufunc struct grew, but unless you subclass ufunc (which nobody really does), it shouldn't be a big issue. But, there may be more to it, I am not too familiar with these build issues. |
Yeah, we now have the |
Sounds like this issue may be solved by upgrading to a newer numpy version, in which 1.3 did bump the dependency. Going to close, but happy to reopen if this continues to be an issue |
Mostly due to old Pandas versions: pandas-dev/pandas#41199 pandas-dev/pandas#32056 pandas-dev/pandas#34848 In one instance, also due to Lark using sre_* modules: lark-parser/lark#1140 Those filters could also be set to `ignore` to not show the warnings at all. This sets them to `default`, restoring the previous behavior of showing the warnings but not failing the test run. Perhaps it might make sense to use older Numpy versions for testing the older Pandas versions too?
Code Sample, a copy-pastable example if possible
Problem description
Although Pandas 1.0.1 has a minimum requirement for numpy of 1.13.3 (see release notes of Pandas 1.0.0), it fails with numpy 1.15.4 (Python 3.6.7).
Problem is solved by upgrading numpy (version 1.18.1 works).
The text was updated successfully, but these errors were encountered: