Closed juliasilge closed 1 year ago
Hi @juliasilge
First of all thanks for your appreciation of our work :)
Honestly, I was thinking about it before and I'm glad you've opened this issue prompting me to rethink this design. Over they years this package has evolved and I agree that keeping reticulate
as a hard dependency does not have much sense nowadays. Therefore I'll be happy to make this change. Will ping you once it it done :)
Hi @juliasilge
It took a while but DALEXtra version with reticulate moved to suggests has been pushed to CRAN last night alongside some refactor :) Let me know if I can help you with anything else!
This is such great news @maksymiuks! ๐ Thank you so much for working on this; it will make deploying explainers for tidymodels much easier. I'll let you know if we run into any other challenges along these lines.
Hello! ๐ Thanks so much for all your great work on this package.
I wanted to ask if you all would be open to moving reticulate to Suggests. This is motivated in particular by how Posit Connect sets up environments for content that requires reticulate (installs Python and tried to create an environment), but I think this will come into play on other deployment targets as well. The idea here is that if you are using tidymodels, you don't need Python and reticulate installed, but if you are using a model like keras, you already have Python and reticulate from dealing with the model itself.
I took a look at how you are using reticulate, and I think you could move reticulate to Suggests if you wrapped calls in
rlang::is_installed()
or used a base R equivalent. For example, your.onLoad()
could become:What would you think about a change like this?