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
Let's face it: people don't do most installation unless they feel there is a need. Saying "install the [coderefinery] conda environment" is quite similar to "install the anaconda environment" and it is easy to think it is already there.
A default anaconda environment seems to mostly work.
Ideas:
See what important packages are missing from the default environment [the only one I saw last week was myst-parser, note it is in conda-forge only]
Add a note saying "want to use your existing conda environment? Do this."
Add notes in the relevant lessons saying what to do if you have a default conda environment (e.g. documentation: conda install -c conda-forge myst-parser)
reproducible-research exercise that explains the coderefinery environment and has people who haven't installed it yet install it? Maybe do it as a demo with pointed reminder to do it before the next day? Shouldn't make people feel bad if they have done it in advance and they are bored then, though.
The text was updated successfully, but these errors were encountered:
I think the install instructions comment enough on this already. Moving this to "reproducible research" lesson for consideration whether it should be an exercise or not.
Let's face it: people don't do most installation unless they feel there is a need. Saying "install the [coderefinery] conda environment" is quite similar to "install the anaconda environment" and it is easy to think it is already there.
A default anaconda environment seems to mostly work.
Ideas:
conda install -c conda-forge myst-parser
)The text was updated successfully, but these errors were encountered: