Description
Describe the feature you'd like
In June 2024, numpy 2.0.0 was released. sagemaker-python-sdk
depends on numpy>=1.9.0,<2.0
. This creates a dependency hell for me, as I have dependencies in my python package that depend on numpy >= 2.0.0
.
You could either enforce numpy >= 2.0.0
and make new releases of the package incompatible with numpy < 2.0.0
or keep supporting the currently supported numpy
versions, but also add those >= 2.0.0
. I.e. depending on whether or not there are breaking changes with numpy >= 2.0.0
in your code base, establish different code paths depending on the installed version of numpy
.
How would this feature be used? Please describe.
Ensuring I can resolve dependencies in Python packages that have both this SDK as well as other dependencies with a requirement for numpy >= 2.0
.
Describe alternatives you've considered
I don't think there is an alternative, as in the long run, this problem will get worse as more and more other packages depend on numpy >= 2.0.0
. I am surprised no one has opened an issue until now.
Additional context
I am also opening a support case with AWS Premium Support.