-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix error with new numpy version #46
Conversation
… demonstrate things are working
The tests seem to fail because of an incompatibility between numpy and pandas, see numpy/numpy#26710 |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #46 +/- ##
==========================================
+ Coverage 97.97% 99.59% +1.61%
==========================================
Files 7 7
Lines 742 738 -4
==========================================
+ Hits 727 735 +8
+ Misses 15 3 -12 ☔ View full report in Codecov by Sentry. |
Roll back numpy dependency in environment.yml as it is not doing anything
…s into fix_numpy_error rebase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me, and thanks for adding the unit tests!
One thing I'm not sure about is the numpy version limit - I think a number of people argued against that as it might make co-updating rail and numpy harder in future versions. People also tend to use the newer versions of numpy, and reverting to older version in order to use rail may be slightly non-ideal.
Having said that, setting numpy<2.0.0
is an effective and short term solution, because the issue presented here seems to be unsolvable within rail, and needs actions from external packages.
Any thought from other reviewers?
pyproject.toml
Outdated
@@ -17,7 +17,8 @@ classifiers = [ | |||
dynamic = ["version"] | |||
dependencies = [ | |||
"deprecated", | |||
"pz-rail-base", | |||
"pz-rail-base>=1.0.3", | |||
"numpy<2.0.0", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to set the numpy version limit?
Another option would be to require |
I just tested setting |
Okay here is the thing: photerr==1.1.0 requires pandas>1.4.3 <2.0.0 |
ok |
np.product doesn't work with the new numpy, so I changed it to np.prod