[
https://issues.apache.org/jira/browse/ARROW-11120?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261997#comment-17261997
]
Laurent commented on ARROW-11120:
---------------------------------
[~npr] I think I understand where I did not understand you, and I think we
agree. (btw, the exchange about "get" / "environment" made me realize that the
R `$` operator/function was not needed since R6 classes inherit from
environment, and that "get" for environments is mapped to the method
`__getitem__` in rpy2 - so thanks!).
While I intend to use rpy2-R6 for what I have in mind, for example conversion
rules for rpy2 or wrapping classes to allow the use of dplyr from Python (like
here https://rpy2.github.io/doc/latest/html/lib_dplyr.html), this does not mean
that everything in the code must be tied to rpy2-R6. My comment about checking
again within few weeks whether there is a part of that code that could live
within the Arrow project was in that sense.
I have cleaned things a bit with the split use rpy2-R6 vs doesn't use rpy2-R6
in mind.
module here:
https://github.com/rpy2/rpy2-arrow/blob/main/rpy2_arrow/pyarrow_rarrow.py
example:
https://github.com/rpy2/rpy2-arrow/blob/main/README.md
> [Python][R] Prove out plumbing to pass data between Python and R using rpy2
> ---------------------------------------------------------------------------
>
> Key: ARROW-11120
> URL: https://issues.apache.org/jira/browse/ARROW-11120
> Project: Apache Arrow
> Issue Type: Improvement
> Components: Python, R
> Reporter: Wes McKinney
> Priority: Major
>
> Per discussion on the mailing list, we should see what is required (if
> anything) to be able to pass data structures using the C interface between
> Python and R from the perspective of the Python user using rpy2. rpy2 is sort
> of the Python version of reticulate. Unit tests will then validate that it's
> working
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
