search

ydataai / ydata-profiling

1 Line of code data quality profiling & exploratory data analysis for Pandas and Spark DataFrames.
https://docs.profiling.ydata.ai
MIT License
12.55k stars 1.69k forks source link

support for numpy >= 2.0 #1645

Closed quant5 closed 1 month ago

quant5 commented 2 months ago

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

stefansimik commented 1 month ago

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.

fabclmnt commented 1 month ago

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?

stefansimik commented 1 month ago

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 ydata-profiling=4.10.0.

Sending screenshot, what happened, when I installed ydata-profiling, to show, that it somehow led to downgrade of numpy.

I installed only ydata-profiling (with ipywidgets), nothing else and this simple operation resulted in downgrade of Numpy.

CleanShot 2024-10-16 at 18 32 05@2x

Note: After some google search, I found out, that the issue could be maybe related to Numba package, which could cause this downgrade: https://github.com/numba/numba/issues/9708

fabclmnt commented 1 month ago

@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.

fabclmnt commented 1 month ago

@stefansimik conda-forge is now fixed: https://anaconda.org/conda-forge/ydata-profiling

stefansimik commented 1 month ago

@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 ❤️