Why sklearn vs scikit-learn? about urbanaccess HOT 3 CLOSED

Ah, that makes sense :)

from urbanaccess.

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.

from urbanaccess.

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

from urbanaccess.