You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Would like to share additional comments here regarding the comment from the MONAI repo.
The problem that everyone has discovered is that their versions strings for Numpy would set a minimum requirement but not a max, so Numpy 2.0 with its incompatibility isn't excluded.
I guess this issue becomes much better when managing packages with conda (especially when using conda-forge) compared to pip.
The dependency issue for us is that we do want to continue supporting older versions of Pytorch because many users may need older versions for compatibility or because their environment requires it. The problem that everyone has discovered is that their versions strings for Numpy would set a minimum requirement but not a max, so Numpy 2.0 with its incompatibility isn't excluded. Older versions of libraries are unlikely to be updated with support for Numpy 2.0, and we have no way of forcing Numpy 1.x when these are present. For the moment we've chosen to just restrict the version although MONAI itself should be compatible now with the changes made.
I appreciate your efforts here. However, it sounds to me like an issue upstream from MONAI, is that correct? Given that MONAI itself, as well as the latest dependencies, is compatible with NumPy 2, I believe that MONAI could fulfill its obligations as long as it reminds users of something like the following in the documentation: If users would like to use certain old versions of dependencies, it may lead to incompatibility with NumPy 2, in which case they should consider downgrading.
Currently, It is impossible to install both MONAI and NumPy 2 with conda due to the constraints in the recipe.
monai-feedstock/recipe/meta.yaml
Line 24 in 7bec2ed
I have found a suggestion from the MONAI repo. However, it only works for pip.
The text was updated successfully, but these errors were encountered: