[pymvpa] RPy and ENET

[Per B. Sederberg]

At Sat, 9 Jan 2010 15:52:47 -0500,
Yaroslav Halchenko wrote:
> 
> Hi Per,
> 
> yeah -- I've tried rpy_classic pretty much with the same "success" ;-)
> 
> I think we should move to rpy2 altogether (rpy adds uncustomizable
> handler for segfaults etc).  And indeed it sounds that glmnet is good
> place to be 'the first bird'.
> 

rpy2 it is!!!  I'll email when I've committed, though it may not be
until tomorrow.

> Per, if you are to start hacking -- please base your changes of mine or
> Michael's masters -- old master (closer to 0.4.3) is way outdated now
> after all underhood changes we had done since 0.4.3 ;)
> 

Definitely, I've merged in both your master branches.  You folks have
done some amazing work on PyMVPA that I've missed during my long
absence from coding land.  I can't wait to start doing analyses again
:) 

Best,
Per

> Cheers,
> Yarik
> 
> On Sat, 09 Jan 2010, Per B. Sederberg wrote:
> 
> > Thus, I propose that we keep LARS and ENET as is with the rpy
> > dependency (we can remove them eventually) and expand glmnet to have
> > both rpy and rpy2 implementations (adding in the rpy2 externals
> > check).
> 
> > If no one objects, I'll go ahead and implement all this.  Let me know
> > if you have suggestions for other ways I should go about handling this
> > rpy business...
> 
> > Best,
> > Per
> -- 
>                                   .-.
> =------------------------------   /v\  ----------------------------=
> Keep in touch                    // \\     (yoh@|www.)onerussian.com
> Yaroslav Halchenko              /(   )\               ICQ#: 60653192
>                    Linux User    ^^-^^    [175555]
> 
>