Re: [Rpy] A terrible experience with rpy2.

2009-04-28 Thread laurent
On Wed, 2009-04-22 at 23:53 -0500, Bo Peng wrote: > On Wed, Apr 22, 2009 at 10:33 PM, laurent wrote: > > On Wed, 2009-04-22 at 12:16 -0500, Bo Peng wrote: > > (...) > > I apologize for the wording of my previous email, which was sent, less > than politely, out of my extreme frustration over a

Re: [Rpy] A terrible experience with rpy2.

2009-04-22 Thread Bo Peng
On Wed, Apr 22, 2009 at 10:33 PM, laurent wrote: > On Wed, 2009-04-22 at 12:16 -0500, Bo Peng wrote: > (...) I apologize for the wording of my previous email, which was sent, less than politely, out of my extreme frustration over a software I had high expectation. However, if you consider all the

Re: [Rpy] A terrible experience with rpy2.

2009-04-22 Thread laurent
On Wed, 2009-04-22 at 12:16 -0500, Bo Peng wrote: (...) > If the correct answer is r('R.Version()').subset('svn rev')[0][0], I > have to say that rpy2 is not for me. 1- There is not "one correct answer". There are several ways to achieve it. Other options are : import rpy2.robjects as ro ro.r

[Rpy] A terrible experience with rpy2.

2009-04-22 Thread Bo Peng
Dear all, I have been a long time rpy user. rpy is *very simple* to use in that you essentially only need to remember two things: 1. Call a R function using r.func(). The only exception is to use _ for . in case that there is a dot in the function name (r.R_Version() for R.Version() and r.dev_off