Okay, revise that... after a closer look at the internals manual, I
realized that lists are VECSXP, not LISTSXP. Silly me, don't know how
I could have mixed that up. Also numpy2ri.py got fixed at some point.
So the only real bug is that newSEXP is still failing to trigger an
exception, which shoul
I just noticed that
import rpy2.rinterface as ri
s_int = ri.SexpVector([1], ri.INTSXP) # works
s_list = ri.SexpVector([s_int], ri.LISTSXP) # appears to work, but
the R object is NULL/Nil
Two issues here:
1) It looks like rinterface.c:newSEXP is trying to throw an exception
rather than sil
On Thu, 2009-04-23 at 16:04 -0300, Donovan Parks wrote:
> Hello,
>
> Are there are any plans to make RPy or RPy2 Windows binaries available
> which are compatible with Python 2.6.x?
The win32 community is not so inclined to contribute them, apparently. I
am personally lacking the necessary time
Hello,
Are there are any plans to make RPy or RPy2 Windows binaries available
which are compatible with Python 2.6.x? I realize it would be easier
to switch to Python 2.5, but we are committed to Python 2.6 for other
reasons. I'd rather not try to compile things myself, but since it may
come to th
There are many posts concerning a memory leak in rpy2, and I have to say
that it's also affecting me.
But fortunately, after losing a couple of days on this problem, I found
this webpage that kind of solve my problem:
http://code.activestate.com/recipes/511474/
The solution is to wrap the work
