Closed csoneson closed 7 months ago
This change was made to avoid a warning concerning library() calls in package source. I will look at this soon.
We are looking at this possible solution, to explicitly qualify the calls to use_condaenv and py_config where they occur:
diff --git a/R/useBasiliskEnv.R b/R/useBasiliskEnv.R
index d5a5ade..93b8590 100644
--- a/R/useBasiliskEnv.R
+++ b/R/useBasiliskEnv.R
@@ -50,11 +50,11 @@ useBasiliskEnv <- function(envpath, full.activation=NA) {
envpath <- normalizePath(envpath, mustWork=TRUE)
activateEnvironment(envpath, full.activation=full.activation)
- use_condaenv(envpath, required=TRUE)
+ reticulate::use_condaenv(envpath, required=TRUE)
# use_condaenv doesn't actually cause Python to be loaded immediately,
# so we force the issue to seal the deal.
- py_config()
+ reticulate::py_config()
invisible(NULL)
}
Considered repaired via 6d0abb9 in devel branch and 6412875 in RELEASE_3_18
Thanks! I pulled down the devel
branch and can confirm that the fix works for me.
We are running into issues with the latest (release 1.14.3/devel 1.15.4) version of
basilisk
, which I think is caused by this change. Basically, after activating the fallback environment,reticulate
functions such asuse_condaenv()
can not be found. For example:If I manually install the
basilisk
version just before the change above, it works fine - it activates the fallback environment, and returns the same vector as when the fallback was not used.cc @ppapasaikas