Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pvlib v0.10.4 is incompatible with numpy 2.0 #2026

Closed
kandersolar opened this issue Apr 30, 2024 · 0 comments · Fixed by #2027
Closed

pvlib v0.10.4 is incompatible with numpy 2.0 #2026

kandersolar opened this issue Apr 30, 2024 · 0 comments · Fixed by #2027
Milestone

Comments

@kandersolar
Copy link
Member

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.

This was referenced Apr 30, 2024
@kandersolar kandersolar added this to the v0.10.5 milestone May 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant