We have been on and off discussing cutting off HMMs. Users use them, have
some success with them and some problems with them. Problems and up in
our tracker, and do not get fixed, because nobody is happy with the code.

We have thought about moving them to another package, but it seems that
no package feels like welcoming this code.

My personal view on the problem is that we need to remove the HMM code.
It is not evolving, cannot be compatible with our own guidelines, and is
drawing resources from the developers. What do people think?

Here is what I propose:

1. Add a DeprecationWarning in the hmm.py code
2. Move the hmm.py code in a separate github repo

Do people agree with this course of action?

Cheers,

Gaƫl

PS: this email originated from the following discussion in the tracker:
https://github.com/scikit-learn/scikit-learn/issues/2578#issuecomment-29295439

------------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general

Reply via email to