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
Numpy 2.0 is coming soon. They released 2.0.0rc1 for testing about a month ago, and a lot of the big downstream python packages have now released wheels that are compatible with it. In particular, all of pvlib's dependencies have numpy 2.0.0-compatible wheels up on either PyPI or the nightly wheels index, meaning we can now effectively test and update pvlib for compatibility with numpy 2.0.
I'm doing that testing now, and it turns out that pvlib can't even be imported with numpy 2.0 due to using np.Inf (not np.inf) as default argument values in some function definitions. That's the most pressing issue, since it means the current version of pvlib cannot be used at all with numpy 2.0. Of course, after getting the import working, there are other issues affecting individual functions as well. I will submit a PR soon that fixes these various issues.
We should make a release containing those fixes before numpy 2.0 comes out. I don't think there is a firm release date for numpy 2.0 yet, but based on the issue linked above, it sounds like it is expected 6-8 weeks after the release candidate, which means mid-late May.
The text was updated successfully, but these errors were encountered:
Numpy 2.0 is coming soon. They released 2.0.0rc1 for testing about a month ago, and a lot of the big downstream python packages have now released wheels that are compatible with it. In particular, all of pvlib's dependencies have numpy 2.0.0-compatible wheels up on either PyPI or the nightly wheels index, meaning we can now effectively test and update pvlib for compatibility with numpy 2.0.
I'm doing that testing now, and it turns out that pvlib can't even be imported with numpy 2.0 due to using
np.Inf
(notnp.inf
) as default argument values in some function definitions. That's the most pressing issue, since it means the current version of pvlib cannot be used at all with numpy 2.0. Of course, after getting the import working, there are other issues affecting individual functions as well. I will submit a PR soon that fixes these various issues.We should make a release containing those fixes before numpy 2.0 comes out. I don't think there is a firm release date for numpy 2.0 yet, but based on the issue linked above, it sounds like it is expected 6-8 weeks after the release candidate, which means mid-late May.
The text was updated successfully, but these errors were encountered: