This pull request introduces a temporary fix for the recent incompatibility issues with NumPy 2.0 by setting an upper limit on the NumPy version in setup.py.
Changes
Updated setup.py to restrict NumPy version to <2.0.
Rationale
NumPy 2.0 includes breaking changes that are currently incompatible with Shapash and other libraries like SHAP. By limiting the NumPy version, we prevent potential issues for users until a permanent compatibility update is available.
Additional Notes
We will continue working on making Shapash compatible with NumPy 2.0 and will remove this restriction once the necessary updates are implemented and tested.
Related Issues
Issue #558
Checklist
[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
This pull request ensures that users will not unintentionally upgrade to NumPy 2.0 and encounter breaking changes. Thank you for your understanding and patience as we work on a more permanent solution.
Temporary Fix for NumPy 2.0 Incompatibility
Description
This pull request introduces a temporary fix for the recent incompatibility issues with NumPy 2.0 by setting an upper limit on the NumPy version in
setup.py.Changes
setup.pyto restrict NumPy version to<2.0.Rationale
NumPy 2.0 includes breaking changes that are currently incompatible with Shapash and other libraries like SHAP. By limiting the NumPy version, we prevent potential issues for users until a permanent compatibility update is available.
Additional Notes
We will continue working on making Shapash compatible with NumPy 2.0 and will remove this restriction once the necessary updates are implemented and tested.
Related Issues
Checklist
This pull request ensures that users will not unintentionally upgrade to NumPy 2.0 and encounter breaking changes. Thank you for your understanding and patience as we work on a more permanent solution.