Hi,
I'm sure you're all burnt out from what looks like a great sprint; thanks
for all that work and congratulations on the RC! So I apologise for the bad
timing.
I am wondering why there is a need to support the indices=False case in
cross_validation. Indices are superior in that they can be used with
np.take and with sparse matrices. And most of the standard cv
implementations output indices that are converted into boolean masks and
back to indices.
Moreover, building generic tools that take cv implementations as input need
to handle both cases (or make assumptions).
What is the intention behind indices=False; why not deprecate it and
simplify the API and code? (And speed up indexing by using np.take.)
- Joel
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
