3 ms·
You can still use pip inside pyenv or similar. Pacman would install the system-wide stuff, so you won't need to bother about the libraries that a package that y
by lucasoshiro 2y ago
You can still use pip inside pyenv or similar. Pacman would install the system-wide stuff, so you won't need to bother about the libraries that a package that you have installed is using.
Mentioning this classic XKCD: https://xkcd.com/1987/ https://xkcd.com/1987/. This only made sense after using a Mac. While using Manjaro it was quite organized: only the pacman-installed libraries and the ones of my user projects. Now in Mac I have the default Python, the several Python versions installed from several dependencies in Homebrew, and so on.
- PittleyDunkin 2y ago> You can still use pip inside pyenv or similar. That seems to be the worst of all possible worlds.
- lucasoshiro 2y agoPerhaps not the best, which could be maybe something like Nix. But this is the opposite of what we have that in Mac
- PittleyDunkin 2y agoI think my point was: > Pacman would install the system-wide stuff Most system-wide stuff is userspace. I was more referring to a divide between the OS-core (kernel, drivers, init scripts) and userspace. Upgrading userspace should not incidentally not allow the system to boot.