On Tue, Dec 03, 2013 at 06:56:14AM +1100, Joel Nothman wrote: > As for "There should be one-- and preferably only one --obvious way to > do it," Gaël, I feel there are times where the one obvious way to do it > should be conditioned on whether you're building an application or > writing a quick script / interactive play.
The problem with pushing that logic too far is that it ends up creating a jump in difficulty going from the interactive use to the proper one. It's a mistake that we did with Mayavi. Ideally, the "correct usage pattern" should be design in a way that it is reasonnably easy to use for interactive use. Going back to the topic of the discussion: if we add an 'api' module, which pattern to we want to document and encourage? G ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk _______________________________________________ Scikit-learn-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
