`R` you ready for python (gentle introduction to reticulate package)’

[This article was first published on R on notast, and kindly contributed to R-bloggers]. (You can report issue about the content on this page here)
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Just like how Thanos claimed to be inevitable in The Avengers, the direct or indirect use of python has become inevitable for R users in recent years. Fret not R users, you don’t have to abandon your favourite IDE, Rstudio, when using python. With the reticulate package you can use python in Rstudio and even have a mixture of R and python code running in the same session. If you blog with blogdown, you don’t have to migrate to another platform to write about your python projects. With the help of reticulate, you can continue publishing content on your blogdown site. An analogy of reticulate will be like a translator between R and python.



reticulate has a default approach to instruct R where to find python, which environment and version to use. There are three approaches to manually configure this.

  1. virtualenv where you specify the directory of python virtual environment

  2. use_python where you specify the path where your ‘python’ resides.

  3. use_condaenv where you specify the name of the specific Conda environment to use. You can access the name(s) of the available environments via conda_list()[[1]]

conda_list()[[1]] %>% use_condaenv()

Let’s check which python version, environment and configuration has been bind to this R session.

py_config() #not run to maintain privacy

Running python

Amend {r} in your code chunk to {python} to run python code. For this post, I will add #{python/r} in my code chunks to make it explicit that I ran the code as a python or a r code chunk.


Plist= [11,22,33,44,55,66]

## [11, 22, 33, 44, 55, 66]

def Psq_fun (x):
  value= x*x 
## 81

Alternatively, you can execute python scripts in your r chunks using the function py_run_string. You will need to wrap your python scripts within the quotation marks “”.


py_run_string("def Pten (x):
          value= x*10

Let’s run the above in a python code chunk.


## 20

Do note that python objects/functions are not explicitly displayed in your global environment (you are after all working in an R global environment by default).


## character(0)

Nevertheless, be assured that you can still access them in future python and r chunks.


## 81

## [11, 22, 33, 44, 55, 66]

Accessing python

You can access previously ran python functions/objects in your r chunks using the prefix py combined with the R’s dollar sign syntax $.


## [1] 16

## [1] 11 22 33 44 55 66

Alternatively, you can directly evaluate previous python objects/functions in r chunks using the py_eval function.


## [1] 11 22 33 44 55 66

## [1] 4

Accessing R

Likewise, you can access R objects/functions in your python chunks using the prefix r combined with a punctuation mark .


## [1] 11 22 33 44 55 66

## [11.0, 22.0, 33.0, 44.0, 55.0, 66.0]

  value= x^.5

## 9.0

Converting objects between languages

Besides accessing a R object in python via r., you can convert the R object into a python object while still running R with r_to_py.

Rvec %>% r_to_py() %>% class()
## [1] "python.builtin.list"   "python.builtin.object"

Previously, I mentioned that python objects do not exist in your global R environment when you run the python script directly inside {python} code chunks or with python_run_string. However, when you create python objects in {r} code chunks, the python object is saved in the R environment.


# convert R object into python 
Python_in_Renv<- Rvec %>% r_to_py()

# check if the converted object lives in the `R` environment. https://stackoverflow.com/questions/1169248/test-if-a-vector-contains-a-given-element
"Python_in_Renv" %in% ls() 
## [1] TRUE

For python objects living in the R global environment, you can convert it back to a R object with py_to_r.

Python_in_Renv %>% py_to_r() %>% class()
## [1] "numeric"


At times you may decide to display R and python code side by side to compare which language is superior.

Html document


The first outlay is static where the page is divided into half and content appears on either half of the page. You will sandwich text and code chunks meant to be on the left and right with the respective html/css code.

#Start of column partition 
<div class = "row">
#Left column
<div class = "col-md-6">
Text: `R` code will be on the left
Chunk of R code ``{r}``

#Right column
<div class = "col-md-6">
Text: `python` code will be on the right
Chunk of Python code ``{python}``

# End of column partition


An alternative will be a where different languages are compartmentalized into their respective tabs and the tabs are displayed next to each another. Users decide which language they wish to view and therefore which tab to highlight. You will use the {.tabset} function with headers to create the tabs and end the tab section with ##.

## Level 2 heading {.tabset}

### Level 3 heading (first tab i.e. left tab)
Text: R code will be on the left tab
Chunk of R code ``{r}``

### Level 3 heading (next tab i.e. right tab)
Text: python code will be on the right tab
Chunk of python code ``{python}``



Unfortunately, the above do not work when building a site with blogdown despite trying several Hugo themes. I’ve adapted code from here which successfully created two columns on this site.

 .col2 {
    columns: 2;

  <div class = "col2">
Text: R code will be on the left 
Code: ``{r}`` 

Text: python code will be on the left 
Code: ``{python}`` 

R code on the left


## function(x){
##   value= x^.5
##   print(value)
##   }

python code on the right


## <function Pten at 0x0000000021361288>

To leave a comment for the author, please follow the link and comment on their blog: R on notast.

R-bloggers.com offers daily e-mail updates about R news and tutorials about learning R and many other topics. Click here if you're looking to post or find an R/data-science job.
Want to share your content on R-bloggers? click here if you have a blog, or here if you don't.

Never miss an update!
Subscribe to R-bloggers to receive
e-mails with the latest R posts.
(You will not see this message again.)

Click here to close (This popup will not appear again)