Re: [Bioc-devel] Python dependency [EXT]

2020-03-26 Thread Daniele Muraro
for your availability. All the best, Daniele From: Martin Morgan Sent: 24 March 2020 19:00 To: Daniele Muraro; bioc-devel@r-project.org Subject: Re: [Bioc-devel] Python dependency [EXT] It's important to ask 'why Bioconductor?' with the answer partly involving

Re: [Bioc-devel] Python dependency

2020-03-24 Thread Martin Morgan
It's important to ask 'why Bioconductor?' with the answer partly involving interoperability with other Bioconductor packages and data representations (e.g., http://bioconductor.org/developers/how-to/commonMethodsAndClasses/). There wouldn't be much value in making something that is essentially

Re: [Bioc-devel] Python dependency

2020-03-24 Thread Hervé Pagès
Hi, Yes Bioconductor packages can depend on Python modules. This should only happen behind the scene and be transparent to the end user (i.e. the end user is not expected to interact directly with the Python module). You can use reticulate (from CRAN) directly or, even better, use basilisk

[Bioc-devel] Python dependency

2020-03-24 Thread Daniele Muraro
To whom it may concern, I would like to upload onto Bioconductor a package which is currently developed in python. I was wondering if Bioconductor supports python dependencies or if I should re-program the package in R exclusively. Is calling python from R using the package "reticulate"