Closed pingretispec closed 1 month ago
Try uninstalling 2.0.0 and installing the latest 1.x version - that fixed it for me:
pip uninstall numpy
pip install numpy==1.26.4
👋 I ran into this issue while working on a rawpy plugin for ImageIO this week, Unfortunately, pinning numpy<2.0.0
is not an option for us, as it would force our downstream libraries into the same pin.
I don't know the intricacies of rawpy's codebase but assuming that it doesn't use any obscure/nitch numpy features this should be solvable by a re-compile and re-release of rawpy for numpy>=2
without any code changes. Is there anything we can do to make this happen? (merging the ImageIO plugin will be blocked until this issue is resolved).
@FirefoxMetzger Releasing a new version built against numpy 2 sounds reasonable. People stuck on numpy 1 will have to pin their rawpy version. Do you want to give this a try in a fork and submit a PR once it's working for you?
I've build rawpy locally against Numpy 2.0 on my Windows machine using python 3.11.
When I run pytest I get the following set of warnings. @letmaik Are these expected or did the switch to numpy v2.0 create them?
Fixed with the latest rawpy release.
Numpy v2.0.0 rawpy v.0.21.0