Include an adoption notice in the deprecation warning?
On Sun, Dec 1, 2013 at 12:49 AM, Gael Varoquaux <
[email protected]> wrote:
> Our poor homeless HMMs. Nobody wants them :)
>
> G
>
>
> --
> Rapidly troub
Our poor homeless HMMs. Nobody wants them :)
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. Wi
On 11/30/2013 01:53 PM, Lars Buitinck wrote:
> 2013/11/30 Vlad Niculae :
>> seqlearn uses a different API on purpose though (one big ndarray),
>> whereas pystruct uses lists of arrays but is only focused on
>> max-margin learning :)
> And seqlearn only does supervised learning.
>
as does pystruct ;
2013/11/30 Vlad Niculae :
> seqlearn uses a different API on purpose though (one big ndarray),
> whereas pystruct uses lists of arrays but is only focused on
> max-margin learning :)
And seqlearn only does supervised learning.
--
seqlearn uses a different API on purpose though (one big ndarray),
whereas pystruct uses lists of arrays but is only focused on
max-margin learning :)
On Sat, Nov 30, 2013 at 12:38 PM, Gael Varoquaux
wrote:
> +1 on the whole thread.
>
> I was hoping that Lars's seqlearn could be a home for poor H
+1 on the whole thread.
I was hoping that Lars's seqlearn could be a home for poor HMMs.
--
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how applicat
> I guess remove means deprecate, right?
> I am +1 but we should definitely find a place for the code. Worse case
> it will be a repo with containing just the HMM.
My thoughts exactly; my impression is that people do find the code
useful and it's reasonably readable. It should definitely go into
On 11/30/2013 12:23 PM, Lars Buitinck wrote:
> 2013/11/30 Kyle Kastner :
>> Does anyone have a consolidated list of API issues with HMM? I have been
>> working with them recently and would be willing to try and work it into
>> better shape, unless core devs would rather have it removed.
> The API o
2013/11/30 Kyle Kastner :
> Does anyone have a consolidated list of API issues with HMM? I have been
> working with them recently and would be willing to try and work it into
> better shape, unless core devs would rather have it removed.
The API of the HMMs is fundamentally different from all othe
Does anyone have a consolidated list of API issues with HMM? I have been
working with them recently and would be willing to try and work it into
better shape, unless core devs would rather have it removed.
On Nov 26, 2013 8:29 AM, "Jaques Grobler" wrote:
> An awkward one to mention..
>
> But,
>
An awkward one to mention..
But,
What are the chances of removing HMMs for the next release.. Issues and PRs
still keep popping up as some users still want it.. but nobody is
maintaining it and as it's been said it doesn't really fit the API/scope..
2013/11/6 Nelle Varoquaux
> It'd be nice to
It'd be nice to merge #2199
Cheers,
N
On 6 November 2013 16:16, Peter Prettenhofer
wrote:
> Given that snow will arrive late I too should be able to get some stuff
> done as well.
>
> I want to get #2570 to MRG within one week so that we have plenty of
> time to review and tweak.
>
> Furthermo
Given that snow will arrive late I too should be able to get some stuff
done as well.
I want to get #2570 to MRG within one week so that we have plenty of time
to review and tweak.
Furthermore, I wanted to have a look a supporting different dtypes for SGD.
@Olivier: I will team up with you on r
2013/11/6 Olivier Grisel :
> I can help prepare the release by going through the open issues and
> pull requests on github and make a summary next week.
>
> All the three PRs highlighted by Gilles seem very important to me. I
> started reading the ESLII chapter on MARS soon to help with the review
I can help prepare the release by going through the open issues and
pull requests on github and make a summary next week.
All the three PRs highlighted by Gilles seem very important to me. I
started reading the ESLII chapter on MARS soon to help with the review
of the PR (I got interrupted by 2 co
Hi,
Thanks for pointing this Andy! I think it would help indeed to set some
coarse deadline for the next release. This would help us get motion and get
things done. End of december or beginning of January would be best for me.
On my side, I don't plan to contribute anything big in the meantime.
Hey everybody.
I just wanted to do my duty and point out that the next release should
be drawing closer.
I'll try to pitch in but I'm not sure how much time I'll actually find.
We are clearly not there at the the moment but I think we should start
to prioritize. I'd really
like the neural net
17 matches
Mail list logo
