You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.
Sounds to me as if it's quite the same thing. I agree to @rbirkelbach that it would be okay to make an event showing both the R and Python version for this as the concepts are pretty much the same. What do you think?
Maybe we should focus on one packaging tool per event. The differing philosophies between different packaging systems seems like they create different concepts to master and skills to learn.
I think it's good to keep this issue separate from issue #28. Maybe it's good to make it into two or three issues. Either teach packrat/miniCRAN and conda together and have another event with docker or have a session with packrat/miniCRAN, one with conda and one with docker. What do you think?
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
eventTopic idea/suggestion for an event. Needs assignee & votes to be scheduled as _post/*.mdPythonR
What should/will the learning objective(s) be?
Learn about packaging R/python software and its dependencies using some of the following tools:
What do participants need to know / install / bring:
Install the tools mentioned above and bring a notebook.
In order to be accepted as an event, each suggestion needs to:
then, a PR can be started against the
_posts
folder to include aYYYY-MM-DD-event-title.markdown
file to actually schedule event.The text was updated successfully, but these errors were encountered: