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 are a couple estimators that are importing sklearn directly and sklearn is not a direct dependency of cuML.
A very quick grep shows imports from sklearn in benchmarks, feature_extraction, preprocessing, & datasets.
We should consider mirroring very trivial imports, such as exceptions, in our codebase so that we don't have any dependencies on Scikit-learn outside of our pytests.
The text was updated successfully, but these errors were encountered:
This issue has been marked rotten due to no recent activity in the past 90d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed.
This issue has been marked stale due to no recent activity in the past 30d. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be marked rotten if there is no activity in the next 60d.
There are a couple estimators that are importing sklearn directly and sklearn is not a direct dependency of cuML.
A very quick grep shows imports from sklearn in
benchmarks
,feature_extraction
,preprocessing
, &datasets
.We should consider mirroring very trivial imports, such as exceptions, in our codebase so that we don't have any dependencies on Scikit-learn outside of our pytests.
The text was updated successfully, but these errors were encountered: