Update setup instructions

[tobyhodges]

This updates the setup instructions for Python, to use Miniforge instead of Anaconda. A recent blog post provides more context for this change.

Two major changes have been made:

1. the page now points to the central Python setup instructions that we maintain as part of the workshop website template repository.
2. The instructions now reflect that we recommend Miniforge instead of Anaconda Python. This means that learners need to activate a carpentries environment before they can launch JupyterLab.

[github-actions]

Thank you!

Thank you for your pull request 😃

🤖 This automated message can help you check the rendered files in your submission for clarity. If you have any questions, please feel free to open an issue in {sandpaper}.

If you have files that automatically render output (e.g. R Markdown), then you should check for the following:

• 🎯 correct output
• 🖼️ correct figures
• ❓ new warnings
• ‼️ new errors

Rendered Changes

🔍 Inspect the changes: https://github.com/LibraryCarpentry/lc-python-intro/compare/md-outputs..md-outputs-PR-149

The following changes were observed in the rendered markdown documents:

 data-visualisation.md |  8 +-------
 getting-started.md    | 31 +++++++++++++++----------------
 index.md              |  2 +-
 libraries.md          |  4 ++--
 md5sum.txt            | 10 +++++-----
 setup.md              | 46 +++++++++-------------------------------------
 6 files changed, 33 insertions(+), 68 deletions(-)

What does this mean?

If you have source files that require output and figures to be generated (e.g. R Markdown), then it is important to make sure the generated figures and output are reproducible.

This output provides a way for you to inspect the output in a diff-friendly manner so that it's easy to see the changes that occur due to new software versions or randomisation.

⏱️ Updated at 2025-03-18 15:55:06 +0000

[chennesy]

Thanks @tobyhodges! A few updates I need to make before merging:

• Update getting-started episode to:
  • remove Anaconda instructions
  • test and then add conda activate carpentries before jupyter lab command for Windows
  • test and add conda activate carpentries for Mac
• Update data-visualisation episode to remove pip install for plotly (plotly is included in env already)

[chennesy]

@tobyhodges Did the task force experience or have guidance related to conda hangups with "Solving Environment..." taking forever? I didn't have any issues on Mac but had to try two or three different workarounds on Windows to get the conda activate carpentries to finish running. Setting the channel priority to strict is what worked for me, but no idea how common this is or if that would help others.

[chennesy]

Thanks @tobyhodges and thanks to the task force for setting up clear guidelines for setting up Python across Carpentries' lessons! This will be a big help, and I hope we've adjusted the lesson as needed to reflect the switch away from Anaconda to Miniforge.

[tobyhodges]

Setting the channel priority to strict is what worked for me, but no idea how common this is or if that would help others.

Hi @chennesy I wanted to circle back to this and ask you to please contribute your experience -- the issue you encountered and the solution your arrived at to address it -- to the wiki page, Configuration Problems and Solutions.

[chennesy]

@tobyhodges Done, thanks!