Practise the standard verbs for isolating Python dependencies with virtualenv.
0 / 5 completed
1 / 5
Fill in: 'We ___ a fresh virtualenv per project so dependencies from one project never leak into another.'
We 'create a virtualenv' — the standard, simple collocation for provisioning an isolated Python environment. The other options are less idiomatic here.
2 / 5
Fill in: 'Installing packages globally instead of in a virtualenv can ___ a conflict between two projects needing different versions.'
We say global installs will 'cause' a version conflict — the standard collocation for the resulting problem. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ the virtualenv before installing any dependencies so pip never touches the system interpreter.'
We 'activate' a virtualenv — the standard, established Python collocation for entering its isolated shell context. The other options aren't the recognised term here.
4 / 5
Fill in: 'We ___ exact dependency versions in a lockfile so a fresh virtualenv always installs the same set every time.'
We 'pin' versions — the standard, established collocation for locking dependencies to exact numbers. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ an unused virtualenv once a project is archived rather than leaving stale environments cluttering disk.'
We 'delete' a virtualenv — the standard, simple collocation for removing an environment no longer needed. The other options are less idiomatic here.