So I have committed a patch that returns None whenever an atomic
NA_integer_ is returned to Python. At least this is better than
returning True.
Atomic integer and real/float are less problematic, so I am inclined to
leave them as they are for now.
The variable NA_{LOGICAL, INTEGER, REAL} are
Nathaniel Smith wrote:
> 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?
>
>
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
> 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
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
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
