3 ms·
Do you have any issues with many virtualenvs/packages taking up a lot of disk space? For instance, numerical packages (scipy, torch, etc) can add up if they’re
by truculent 4y ago
Do you have any issues with many virtualenvs/packages taking up a lot of disk space?
For instance, numerical packages (scipy, torch, etc) can add up if they’re duplicated across many projects, and, as I understand it, virtualenv doesn’t do any caching/symlinking.
- Zizizizz 4y agoI don't work on too many projects at a time and tend to archive and remove the virtualenv when I finish working on something for the foreseeable future. I can see why that would be a problem for some though.
- fbdab103 4y ago>...virtualenv doesn’t do any caching/symlinking. Well, one of us is incorrect then. I had been thinking for years that one of the key benefits was that virtualenv would not do a blind copy of files (except on Windows...sigh). The `venv` command even has a `symlinks` vs `copies` option. `python3 -m venv --help`
- truculent 4y agoSorry, this was my mistake - I ought to have said that pip doesn't cache/symlink installed packages (unless I am wrong about this also!). You are, of course, correct that the python binaries are symlinked.