It would also be worth looking at the basilisk package:
https://github.com/LTLA/basilisk
where the approach used there is to instead embed a Conda installation
as part of the R package itself. This comes with the benefit that it's
now the package author's responsibility to maintain the Conda
inst
On Tue, Jan 7, 2020 at 10:42 PM Sokol Serguei wrote:
>
> Thanks for this hint.
>
> Le 07/01/2020 à 20:47, Kevin Ushey a écrit :
> > The newest version of reticulate does something very similar: R
> > packages can declare their Python package dependencies in the
> > Config/reticulate field of a DES
Le 08/01/2020 à 08:50, Ivan Krylov a écrit :
On Tue, 7 Jan 2020 15:49:45 +0100
Serguei Sokol wrote:
Currently, many R packages include TPS as part of them thus bloating
their sizes and often duplicating files on a given system. And even
when TPS is not included in an R package but is just ins
On Tue, 7 Jan 2020 15:49:45 +0100
Serguei Sokol wrote:
> Currently, many R packages include TPS as part of them thus bloating
> their sizes and often duplicating files on a given system. And even
> when TPS is not included in an R package but is just installed on a
> system, it is not so obvious
Thanks for this hint.
Le 07/01/2020 à 20:47, Kevin Ushey a écrit :
The newest version of reticulate does something very similar: R
packages can declare their Python package dependencies in the
Config/reticulate field of a DESCRIPTION file, and reticulate can read
and use those dependencies to pr
The newest version of reticulate does something very similar: R
packages can declare their Python package dependencies in the
Config/reticulate field of a DESCRIPTION file, and reticulate can read
and use those dependencies to provision a Python environment for the
user when requested (currently us
