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
There seems to have been some changes in scikit-learn's new version (0.24): I have the following errors ModuleNotFoundError: No module named 'sklearn.utils.testing' when calling pytest on metric-learn (after a fresh clone of master on a conda env with scikit-learn 0.24). The reason is the one from this comment uber/causalml#285 (comment):
The sklearn.utils.testing module is deprecated in version 0.22 and will be removed in version 0.24. The corresponding classes / functions should instead be imported from sklearn.utils. Anything that cannot be imported from sklearn.utils is now part of the private API.
The text was updated successfully, but these errors were encountered:
Indeed! We can also still import private functions from sklearn.utils._testing
We should however ensure back-compatibility with previous versions of sklearn (since we allow scikit-learn>=0.20.3). One option is to do something similar to uber/causalml#283
Indeed! We can also still import private functions from sklearn.utils._testing
We should however ensure back-compatibility with previous versions of sklearn (since we allow scikit-learn>=0.20.3). One option is to do something similar to uber/causalml#283
Thanks for the reference @bellet, I just opened a PR to try fix the imports using this technique, and add the travis job to ensure it is indeed still back-compatible #313
There seems to have been some changes in scikit-learn's new version (0.24): I have the following errors
ModuleNotFoundError: No module named 'sklearn.utils.testing'
when calling pytest onmetric-learn
(after a fresh clone of master on a conda env with scikit-learn 0.24). The reason is the one from this comment uber/causalml#285 (comment):The text was updated successfully, but these errors were encountered: