Review of virtual environments and dependencies episode

[steve-crouch]

• Objectives: something on semver?
• “cd 2020-se-day4/code” -> remove “2020-“ prefix
• “package to coexist on your machine and only one to be selected for each of your projects” - feel that ‘selected’ is a bit ambiguous on what is meant in practice - perhaps “selected and used” or just “used”?
• “…is to set up 2 Python virtual environments” - perhaps add for clarity “, one for each version of Python.”?
• “Since we’ve been installing everything so far, in virtual environments, there shouldn’t be anything installed in your main version of Python” - I found with no activated virtual environment on the new SABS VM I actually got a list of about 70 os-wide installed Python packages
• “Try activating one of our previous virtual environments, or creating a new one and installing a few packages to see if they show up now.” - I’d maybe add a brief summary commands for this, or at least in a separate paragraph, so it doesn’t get missed.
• “Let’s say we want to try out the latest version of Python (3.10 at the time of writing)” - update the Python version to use?
• “pyenv install 3.10” - I needed to use “3.10.0” for the version to be properly identified
• “python version” - I needed to use “python3” - “python” got a not found; e.g. “python3 --version”
• Keypoints: would be good to have some more e.g. on requirements files, semver, the pyenv tool, etc.

[jag1g13]

Addressed in 7489f7a