Re: [Rpy] RPy for Py3k ?

I don't know much about the architectural decisions of rpy2, but, If rpy2 were standing on top of ctypes instead of directly implementing a c interface, it would be easier to go up along with the python version upgrades. On Wed, Jan 28, 2009 at 12:49 PM, Alex Mandel wrote: > 조성일 wrote: >> Hello,

Re: [Rpy] RPy for Py3k ?

조성일 wrote: > Hello, > > I understand python 3.0 is going to be the future standard. > Is there a plan to develop RPy for python 3.0 soon? > Currently RPy2 requires python 2.x, and doesn't seem to work with 3.0. I am > wondering whether I should hold on to python 2.x, or move to py3k and > wait for

[Rpy] RPy for Py3k ?

Hello, I understand python 3.0 is going to be the future standard. Is there a plan to develop RPy for python 3.0 soon? Currently RPy2 requires python 2.x, and doesn't seem to work with 3.0. I am wondering whether I should hold on to python 2.x, or move to py3k and wait for a new RPy. I couldn't e

Re: [Rpy] Handling of NA w/ get()

On Tue, Jan 27, 2009 at 1:02 PM, Jeff Gentry wrote: >> I am also getting: >> >>> robjects.r('NA')[0] >> True > > So does this imply that R's NA objects always evaluate as Python's True > right now? What is (or should be) the equivalent to a NA value in Python? Heh, I was just researching this l

Re: [Rpy] Handling of NA w/ get()

> Good to see Bioconductor veterans here ! ;-) Hah. :) I hadn't realized until after I sent my message that you're the main developer for Rpy2. I stumbled across Rpy2 after stumbling across Rpy after looking into Duncan's RSPython package. > > Is this expected behavior (True replacing NA)? > De

Re: [Rpy] [patch] enhance console callback API

Nathaniel Smith wrote: > On Mon, Jan 26, 2009 at 3:22 AM, Laurent Gautier wrote: >> Nathaniel Smith wrote: >>> There are a number of callbacks in rinterface that one can set to >>> control R's console -- setWriteConsole, setReadConsole, etc. This >>> patch fixes to limitations with the current API

Re: [Rpy] Handling of NA w/ get()

Jeff Gentry wrote: > Hi there ... > > I was looking to work with some of the Bioconductor annotation packages > directly in Python and came across Rpy2. Good to see Bioconductor veterans here ! ;-) Rpy2 should/will do more with BioC (but more some time later). > The first problem is just one of

[Rpy] Handling of NA w/ get()

Hi there ... I was looking to work with some of the Bioconductor annotation packages directly in Python and came across Rpy2. The first problem is just one of inexperience, I'm probably doing things all wrong and that could be the source of my issue :) I did just notice something odd: t = robje