-
Notifications
You must be signed in to change notification settings - Fork 112
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
Work around bug in pint 0.24.0 #534
Labels
ci
Continuous integration
Comments
This also affects |
khaeru
added a commit
that referenced
this issue
Jun 17, 2024
2 tasks
khaeru
added a commit
that referenced
this issue
Jun 17, 2024
khaeru
added a commit
that referenced
this issue
Jun 17, 2024
khaeru
added a commit
that referenced
this issue
Jun 17, 2024
2 tasks
This was closed in #544. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pint 0.24.0 (released 2024-06-) triggered CI failures like this:
This was due to hgrecco/pint#2007 affecting this line:
ixmp/ixmp/report/operator.py
Lines 124 to 126 in 35da509
Work-around / mitigation
Limit pint to < 0.24.
At Use pint != 0.24.0 in "pytest" CI workflow #535, with pint 0.23 and NumPy 2.0.0, we see:
This is mentioned at pint 0.24 / numpy 2.0 / python 3.9 issues hgrecco/pint#1974 (comment).
Because of this (but for no other reason, i.e. no issue inherent to ixmp), the mitigation also requires to limit NumPy < 2.
Fix
Wait for the release, confirm the fix, remove the work-around, and close this issue.
The text was updated successfully, but these errors were encountered: