-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
support for numpy >= 2.0 #1645
Comments
This is really important. This library already forces us to downgrade to older Numpy versions and it is not very comfortable situation. Starts to be blocker for using this library. |
This issue is closed since release 4.10 (Sep 7th) - https://github.com/ydataai/ydata-profiling/releases/tag/v4.10.0, where numpy has been bump. @stefansimik which version of the package are you using? |
I am using Sending screenshot, what happened, when I installed ydata-profiling, I installed only ydata-profiling (with ipywidgets), nothing else and this simple operation Note: |
@stefansimik, thanks for sharing that information it was super helpful to identify the source of the issue. The latest version of the package is now in 4.11.0 (https://pypi.org/project/ydata-profiling/), so there is something happening with the anaconda repo. I'll check with the team, but I do suggest that you use Pypi instead for the time being. |
@stefansimik conda-forge is now fixed: https://anaconda.org/conda-forge/ydata-profiling |
Excellent work 👍 , I really appreciate your effort and how quickly you solved this ❤️ |
I'm getting ImportError: Numba needs NumPy 2.0 or less. Got NumPy 2.2. in the last release, is this normal =? |
Getting the same issue as above even after downgrading to 2.0. The |
Get the same error: Version:
From this line: |
Missing functionality
Numpy 2.0.0 was released on June 16. https://github.com/numpy/numpy/releases/tag/v2.0.0. The current version is 2.1.1.
To date, ydata-profiling is not compatible with 2.0.x per
requirements.txt
.As such, it is currently a blocker for users to upgrade to 2.0.x if they have this package installed.
Proposed feature
Loosen requirements to include 2.0.x unless there are specific reasons (e.g., usage of deprecated function names) not to.
Alternatives considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: