feat: add callout to set venv in VS Code

[amangoel185]

• Add callout to set the virtual environment in VS Code
• Reference: https://carpentries-incubator.github.io/python-intermediate-development/instructor/aio.html#adding-a-python-interpreter
• Will fix Add a callout on how to save virtual env settings in VS Code for the project workspace #301
• Need to update the VS Code screenshots

[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/carpentries-incubator/better-research-software/compare/md-outputs..md-outputs-PR-329

The following changes were observed in the rendered markdown documents:

 03-reproducible-dev-environment.md      |  27 +++++++++++++++++++++++++++
 fig/vscode-interpreter-path.png (new)   | Bin 0 -> 539453 bytes
 fig/vscode-interpreter-venv.png (new)   | Bin 0 -> 853717 bytes
 fig/vscode-select-interpreter.png (new) | Bin 0 -> 508721 bytes
 md5sum.txt                              |   3 +--
 5 files changed, 28 insertions(+), 2 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-11-20 11:42:07 +0000