Development workflow for R+Python packages

Is there an efficient workflow for developing R packages that use actively developed python modules as well? I am developing an R package that wraps some legacy python code. As I work on the R side of things I find myself refactoring the python code as well. For these changes to be accessible to R, restarting the session doesn't seem to work.

I have been resorting to terminating the R session completely so that whatever reticulate does when it starts up, can be performed fresh. This is incredibly cumbersome compared to the breezy ctrl+shift+L when developing an R package using devtools. Which leads me to this post. Am I doing something wrong? Can jointly developing a package in R + Python be as smooth?

1 Like

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.