VertexWiseR uses Python functions from various toolboxes that can flexibly be called and executed in R using the reticulate package (Ushey, Allaire, and Tang 2023). We explain in this article how to solve a number of issues that may arise from the interaction with Python.
As explained in the home page, this is a pop-up or prompt from the reticulate package. Choosing ‘Yes’ will let reticulate install Python in a virtual environment. This is entirely optional. Simply choose/click No/Cancel to ignore.
The reticulate documentation explains:
When installing Python packages it’s best practice to isolate >them within a Python environment (a named Python installation >that exists for a specific project or purpose). This provides a >measure of isolation, so that updating a Python package for one >project doesn’t impact other projects. The risk for package >incompatibilities is significantly higher with Python packages >than it is with R packages, because unlike CRAN, PyPI does not >enforce, or even check, if the current versions of packages >currently available are compatible.
Note that VertexWiseR will install a stable specific version of Python itself and of each package it needs to work properly. If users believe they will be using the Miniconda/Python installation for more than VertexWiseR and will need to update them, it may be safer to install a specific Miniconda/Python environment in a path of their choice (as allowed by VWRfirstrun()), or to use a reticulate isolated virtual environment. More details on why using virtual environments can be found in the reticulate documentation.
VertexWiseR will automatically select and run a Python installation
it finds via reticulate, but users may want to prevent this and run
VertexWiseR on a new Python installation of its own. This section
explains how to make VWRfirstrun() ignore a previous
Python/Miniconda installation in order to install a new one (which will
not affect the system’s Python libraries).
Firstly, the Python installation path may already be preloaded in the
global environment, via files such as .Renviron,
.Rprofile, .bashrc etc. If that is the case
they should be edited to remove the path of a previous Python
installation, which will avoid reticulate from using those paths
automatically.
Secondly, if the Python paths are not specified in the global environment, reticulate will then search for a Python installation in its default locations. This can be avoided with the method below.
To make VWRfirstrun() ignore a previous Python
installation, users can set the RETICULATE_PYTHON variable
as NA (in a new R session with a clean workspace) before
running the function:
With the above lines, reticulate should fail to load Python and
respond in the same way it would if Python was not previously installed
at all. Therefore, VWRfirstrun() will prompt users to
install a new Python environment. After that, VWRfirstrun()
will use that newly installed Python environment by default and users
should not need to do this again.
This section explains how users can choose a different Python other than the one automatically detected if they wish to, instead of installing a new one.
Reticulate allows users to predefine the Python environment to be used by entering their Python’s directory path into the following functions:
reticulate::use_python(python)
reticulate::use_virtualenv(virtualenv)
reticulate::use_condaenv(condaenv)
reticulate::use_miniconda(condaenv)These functions must be executed before VWRfirstrun() is
run in the R session. The latter function should then automatically
assume that a version of Python is correctly installed and only ask for
other packages to be downloaded/installed if they are missing. To check
the Python installation that is being used, users can run:
This will print the information and path of the Python environment reticulate is currently using. If that is still not the path specified in the functions listed above, users should try restarting R and/or clearing the R workspace first.
If Python or Miniconda was already installed using
VWRfirstrun(), users will not be able to modify the Python
path in the above manner. That is because the path to the user-selected
default or custom installations is saved in order to conveniently access
them again later. Every time VWRfirstrun() is run, it will
read and use such saved paths. This also depends on whether the user
created a default ephemeral environment or chose a manual
Python/Miniconda installation.
The paths to these installations are saved inside the
.Renviron file, in the standard path generated via:
Within the .Renviron file, the environment variables
will be written in this manner:
RETICULATE_MINICONDA_PATH="C:/path_to_miniconda/"
RETICULATE_PYTHON_FALLBACK="C:/path_to_miniconda/"
RETICULATE_PYTHON="C:/path_to_miniconda/python.exe"To swap with another Python environment, users may choose to edit
.Renviron directly, by replacing the paths with the Python
installation they would like VertexWiseR to use instead. The
RETICULATE_MINICONDA_PATH may also be safely removed if a
non-conda Python library is to be used. Alternatively, users may choose
to completely remove the .Renviron and redefine the path as
described in section 3a.
This is in the case that users chose the virtual environment installation proposed by VWRfirstrun(), which calls reticulate::py_require(). The path to such environment is accessible with that command line:
To stop using this environment, users may choose to clear the cache completely:
If they do not wish to get rid of the previous virtual environment,
users will have to modify and/or remove the VIRTUAL_ENV variable which
has been stored in the .Renviron file, in the standard path
generated via:
This variable is automatically removed when the virtual environment can no longer be found in the cache, but will automatically be used by VWRfirstrun() after its installation to speed up the process, if it still exists. So the VIRTUAL_ENV variable must be rewritten to the new ephemeral environment generated by py_require() to use the latter.