Aaron Lun

The error messages suggest that the various conda scripts are not being executed with `bash`, given that `sh` doesn't know anything about `[[`. I have no idea how it got...

Thanks for the update @bschilder. It may be worth looping in some other **basilisk** users who work on GitHub; @kevinrue @alanocallaghan @lazappi @vjcitn etc. Maybe they have some experience with...

This is, unfortunately, a fairly difficult problem. Here is my diagnosis: Normally, the conda installation comes packaged with its own libstdc++. This guarantees that any conda packages (and the conda-packaged...

> Why? Python 3 is on almost every system those days, and, if not (e.g. on Windows) is super easy to install. The minor version matters, e.g., pandas 1.4.3 requires...

From some testing on the BioC-devel Docker image, it seems that conda is grabbing the very latest acceptable version of **scipy**. This version requires a later version of libstdc++ than...

It seems that the build system is not without a sense of irony: http://bioconductor.org/checkResults/devel/bioc-LATEST/basilisk/nebbiolo2-checksrc.html In particular: ``` Running ‘testthat.R’ ERROR Running the tests in ‘tests/testthat.R’ failed. Last 13 lines of...

Fixes to **basilisk** (and **basilisk.utils**) have been pushed to BioC-devel. It doesn't really "solve" the `GLIBCXX` mismatch but it provides a fallback mechanism to execute **reticulate** code that relies on...

Oops. Hopefully 1.9.10 will fix this. Try installing **basilisk** from GitHub if you want it sooner.

Thanks Kevin; > Right now, our intention is to download and install Miniconda onto the user's filesystem (using a path from [rappdirs](https://cran.r-project.org/web/packages/rappdirs/index.html)), which can then be discovered and used by...

That's an interesting perspective. I hadn't realized that the Python objects were persistent like that. If I may throw another opinion into the ring: for the packages I develop, I...