On Sat, Sep 24, 2011 at 3:17 AM, Skipper Seabold <[email protected]> wrote:
> I thought the main goal when we started talking about dropping scikits > was simply to avoid having namespace packages. It sounds like this is > no longer the focus? We asked on the ML what import name people liked best, and there was a large consensus for "sklearn" over "learn". The main problem of "learn" was that it is too generic. This probably holds for "image" and "data" too. Also several people agreed that we should keep promoting the scikit branding, hence the "scikit-" prefix in the project name. Ideally we would have: - scikit-learn (import sklearn) - scikit-image (import skimage) - scikit-data (import skdata) - scikit-statsmodel (import skstatsmodel) etc... Mathieu ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2dcopy2 _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
