Skip to content
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

Why sklearn vs scikit-learn? #27

Closed
kuanb opened this issue May 10, 2017 · 3 comments
Closed

Why sklearn vs scikit-learn? #27

kuanb opened this issue May 10, 2017 · 3 comments

Comments

@kuanb
Copy link
Member

kuanb commented May 10, 2017

[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

@pksohn
Copy link
Collaborator

pksohn commented May 10, 2017

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.

@kuanb
Copy link
Member Author

kuanb commented May 10, 2017

Ah I see it was updated a few days ago: ff1cfe9

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).

@pksohn
Copy link
Collaborator

pksohn commented May 10, 2017

Ah, that makes sense :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants