-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Fixes for tests on nightly builds of numpy/scipy/pandas #6897
Conversation
26eaa93
to
ed02e75
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #6897 +/- ##
==========================================
- Coverage 88.21% 88.20% -0.01%
==========================================
Files 326 326
Lines 71264 71266 +2
==========================================
Hits 62863 62863
- Misses 8401 8403 +2 |
8347967
to
696c942
Compare
973111f
to
f93e022
Compare
The optimizer in scipy changed. The correct final result is still the same. The problem is that Logistic Regression has a quite small default |
066088a
to
ec7fa0a
Compare
ec7fa0a
to
c57931c
Compare
This is a proper solution that would work before and would continue to work in pandas>=3 -- if it was not for a bug in pandas (pandas-dev/pandas#59913). Hence, this commit also (dynamically) patches the bug in pandas.
c57931c
to
85638d9
Compare
Issue
Scientific Python nightly wheels fails.
Description of changes
NAN
andINFTY
fromlibc.math
instead of fromnumpy.math
. This caused an error in cythonizing.test_pandas
, do not importpytz
. We do not (directly) depend on it, and pandas removes it in 3.0.<M8[s]
instead of<M8[ns]
. We convert this to floats containing seconds from epoch, so it doesn't affect us. A test failed just because it expected to see<M8[ns]
, so I changed the test.OrangeDataFrame
, but for pandas < 3 it dynamically patches the bug in pandas. The patch can be removed when we raise pandas requirements to 3.0.To be fixed elsewhere