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
In preparation for the workshop we were thinking that it would be nice to offer some summarizing exercise in the end of the workshop, where everything or most of what was learned can be applied.
Another idea would be to team up participants (preferably with different OS) in teams of 2, and let them go through a workflow similar how it could go in a project with different steps:
First, both create an environment (packages could be suggested by material), write or export an environment.yml without version numbers and share with partner, partner creates environment from file and results are compared (to notice the differenced coming from low level os dependent packages, possibly version differences,...). Then same with version numbers.
Could make use of some diff tool to explore differences of environments.
This could then also be taken even further as discussed with @davidrpugh , @annefou, @naoe-tatara and toby today to go towards actually finding a package with some deprecated function call and let the learners build an environment for that case with provided code to test if it works and to see how the error messages may look.
Happy to discuss different possibilities of a summarizing exercise here :)
The text was updated successfully, but these errors were encountered:
In preparation for the workshop we were thinking that it would be nice to offer some summarizing exercise in the end of the workshop, where everything or most of what was learned can be applied.
@bast created one such exercise here: https://github.com/coderefinery/conda-exercise
Another idea would be to team up participants (preferably with different OS) in teams of 2, and let them go through a workflow similar how it could go in a project with different steps:
First, both create an environment (packages could be suggested by material), write or export an environment.yml without version numbers and share with partner, partner creates environment from file and results are compared (to notice the differenced coming from low level os dependent packages, possibly version differences,...). Then same with version numbers.
Could make use of some diff tool to explore differences of environments.
This could then also be taken even further as discussed with @davidrpugh , @annefou, @naoe-tatara and toby today to go towards actually finding a package with some deprecated function call and let the learners build an environment for that case with provided code to test if it works and to see how the error messages may look.
Happy to discuss different possibilities of a summarizing exercise here :)
The text was updated successfully, but these errors were encountered: