-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revisit package dependency handling #21
Comments
I have reviewed the different alternatives for package dependency handling. It seems the main options are:
I also reviewed other alternatives, such as Docker and Posit, but these don't seem to suit our purposes well. Docker may still be an alternative in specific projects that become too large for My sense is that even though If we agree on which is the best option, I can work on setting up a simple template environment. I am also happy to keep investigating and run any more tests if you have questions or suggestions. |
Thanks @lucamlouzada. A few thoughts:
|
This issue is part of an effort to implement substantive improvements to the lab template, as discussed in #16.
In this issue, the goal is to evaluate different alternatives for managing software and package dependencies and choose the best approach. The main points to be addressed per the decision in plans for next steps are:
Decision:
renv
for managing R packages andvenv
(or something similar) for Python. Play with the alternatives yourself and evaluate its pros and cons.I am assigning myself to work on this. I will start by researching different alternatives and evaluating pros and cons. After we have settled on the preferred approach, I will implement and test.
The text was updated successfully, but these errors were encountered: