Hi all, I think we should re-think our utils model. Currently, it's a mish-mash of tools for development (e.g. array2d, logsum, etc.) and performance code that's better than many other available python implementations (e.g. fast_svd, graph_shortest_path, etc.). As far as I can tell, none of this is well represented in the html docs.
I propose creating a subsection of the developer's doc page outlining the utils available and when/why/how they should be used. I'd also like to move the more substantial utils to another folder, perhaps sklearn/enhancements, and document them in a separate section of the html docs. I think this could lead to some wider use of the scikit-learn optimized methods - i.e. if someone is on the web searching for "python fast svd", they may find our page and use the scikit. Currently, the methods are so hidden that they likely wouldn't be found. Thoughts? Jake ------------------------------------------------------------------------------ Learn Windows Azure Live! Tuesday, Dec 13, 2011 Microsoft is holding a special Learn Windows Azure training event for developers. It will provide a great way to learn Windows Azure and what it provides. You can attend the event by watching it streamed LIVE online. Learn more at http://p.sf.net/sfu/ms-windowsazure _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
