In response to #2630 by Jason Rudy, Gaël suggested discussing deficiencies
in the Pipeline API as a big picture. He suggested this might lead to a
better solution than hacking in each change individually. IMO, this may
also be valuable to ensure consensus and understanding, without which we
have lingering, un-merged PRs.
I have collated the issues I could recall or find, although there may have
been others discussed. They are described at
https://github.com/scikit-learn/scikit-learn/wiki/Pipeline-et-al.-design-issues.
Please let me know what is missing, and I guess we should consider/propose
solutions!
- Joel
------------------------------------------------------------------------------
Sponsored by Intel(R) XDK
Develop, test and display web and hybrid apps with a single code base.
Download it for free now!
http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
Scikit-learn-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
