ri_session can load the wrong python version

[jspijker]

If a conda environment is used (reticulate::use_condaenv), then the py version is not loaded due to the system("which ..") call (which often returns the system wide py version)

[jspijker]

Apparently, reticulate lazy-loads the condaenv. So only after an API call, the conda env is used. Hence, before an API call the system wide python version is used in use_python.

Calling e.g. py_config, it does an API call, after which the right conda environment is used. However, when no python conda environment is present (and thus, the system wide py shoudl be used) reticulate asks if it should create a conda env (r-reticulate). This confuses users who are not used to conda (and work on systems without conda environments).

The only way to solve this is to either add an extra configuration step before ri_session, so the user can set the right python environment, or to use conda envs by default (and this environment must be present on package load, or set during package load)