Add a teaser on uv

[fnattino]

At first, I have started on making uv the tool used throughout the episode by adapting all venv/pip commands (essentially adding uv in front of these) - but then I thought it could still be instructive to use the built-in tools here and point to uv as one of the possible options? I mean, commands like uv venv and uv pip make much more sense if you have used venv and pip before. Similarly, you appreciate uv run, after having to activate the environment before calling Python.

So, I have ended up only adding a callout onuv, suggesting it as the tool to try out when in doubt on what to experiment with.

What do you think?

[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/esciencecenter-digital-skills/python-intermediate-development/compare/md-outputs..md-outputs-PR-4

The following changes were observed in the rendered markdown documents:

 12-virtual-environments.md | 35 ++++++++++++++++++++++++++---------
 md5sum.txt                 |  2 +-
 2 files changed, 27 insertions(+), 10 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-10-22 10:51:11 +0000

[sjvrijn]

I think this is fine for now. You're right that since uv [venv|pip] is a drop-in replacement, there is no strict necessity to include it here. Same goes for the associated speed-up, or for having it already installed by the time we reach the packaging section: might be nice, but not needed.

I'm okay with seeing how it goes and perhaps adjusting the material afterwards again based on our experience.