You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: On OSX with a virtualenv named "venv" and an anaconda installation in the background (outside of venv)
Problem: Importing my python module as reticulate::import("mymodule") was complaining about not being able to find matplotlib even after running use_virtualenv("/Users/me/mypackage/venv"). This problem occurred in Rstudio but did not occur from a terminal R session initiated inside of the activate virtual environment.
Temporary solution: Basically the same as suggested in #367, which is to tell reticulate to look inside of venv/bin by updating the system PATH before loading the library:
Running py_config() showed that it was pointing to a random conda environment. I don't see how my virtualenv could have become associated with that conda env. Anyway, I removed that conda env and now my virtualenv works again with use_virtualenv.
Context: On OSX with a virtualenv named "venv" and an anaconda installation in the background (outside of venv)
Problem: Importing my python module as
reticulate::import("mymodule")
was complaining about not being able to find matplotlib even after runninguse_virtualenv("/Users/me/mypackage/venv")
. This problem occurred in Rstudio but did not occur from a terminal R session initiated inside of the activate virtual environment.Temporary solution: Basically the same as suggested in #367, which is to tell reticulate to look inside of venv/bin by updating the system PATH before loading the library:
The text was updated successfully, but these errors were encountered: