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
Hey Kuan,
The list of required packages in setup.py refers to the right package, scikit-learn. The import syntax just uses the shortened name, sklearn, as seen in the quick start guide.
Closing this for now - let us know if there's something we missed here.
I had not pulled the latest commits to master. Prior to that commit, looks like the lib was indeed using sklearn vs. scikit-learn. Since the author is listed as "Unknown", I had thought that perhaps you guys had set that up as a sort of proxy to scikit-learn and was wondering why that was done (if that was the case).
[Ques] According to the package page, one should use scikit-learn, rather than sklearn. Is there a specific reason why sklearn is being used, instead?
Ref: https://pypi.python.org/pypi/sklearn/0.0
The text was updated successfully, but these errors were encountered: