On Mon, Sep 17, 2012 at 8:40 PM, Ariel Rokem <aro...@gmail.com> wrote:Don't forget the author of %%R is just down the street from you :) He
> OK - that makes sense. I get some things to appear on the R side, but not a
> proper data frame. My knowledge of R is pretty rudimentary, so I am afraid I
> can't be much help.
might be up to a little sprint on the matter if you ping him.
If not, we could try to make it happen in a couple of weeks, I suspect
I'll be paying you guys a visit soon.
Hi Fernando,On Thu, Sep 20, 2012 at 5:13 PM, Fernando Perez <fpere...@gmail.com> wrote:
On Mon, Sep 17, 2012 at 8:40 PM, Ariel Rokem <aro...@gmail.com> wrote:Don't forget the author of %%R is just down the street from you :) He
> OK - that makes sense. I get some things to appear on the R side, but not a
> proper data frame. My knowledge of R is pretty rudimentary, so I am afraid I
> can't be much help.
might be up to a little sprint on the matter if you ping him.OK - following your prompting, I took another look at this. The truth is that we seem to be very close to have this working. Take a look here (cell 32 and onwards are changed relative to the example Jonathan wrote):The problem right now is that pandas sets the dtype for columns that are strings as 'object' and then R doesn't quite know what to do with that (or does something that I don't understand). Wes - is there a particular reason that pandas does that?I am actually pretty happy with the current state of affairs, by using this kind of hack of manually fixing the dtype for string columns, I could make my own use-case work beautifully. No more writing/reading to csv files...But it would be nice to make this automatic.