Hello Metaflow team, thanks for sharing this project with the community. We are currently developing a R package that relies on several Python dependencies. I believe our packages are taking a similar approach to managing the Python deps. To be specific, my package is setting up a conda or virtual environment with a specific name, installing the deps within it, then using

reticulate::use_*env

or

reticulate::use_python

to activate the environment for use with the R package. When I try to test a flow that loads our package, it seems to fail at the step where my package is trying to find the Python environment it needs. I have attached a script and the error message, however, please know that the package I'm loading is not available to the public yet. I can share any code that might be helpful for understanding the problem. Do you have any general advice on how to use

reticulate

and Python within R packages so that they operate smoothly with other R packages that have their own Python dependencies? In addition, are there any Metaflow-specific adjustments I could make to my package to enable interoperability? Best, Justin