3 ms·
The way it's meant to be. On Linux, you either use the system packages via "apt install", or you use venvs. EDIT: For context, I've meant "managed" distros li
by wheelerof4te 4y ago
The way it's meant to be.
On Linux, you either use the system packages via "apt install", or you use venvs.
EDIT:
For context, I've meant "managed" distros like Debian and Ubuntu.
- qbasic_forever 4y agoNowhere in the official Python documentation (where 99% of new python users are going to go) does it warn or even talk about Linux and Debian specific issues like only using apt packaged versions of dependencies. It wasn't even until recent years that pip gave a hint or warning something might break in those setups. The situation with Python on Debian has been pretty bad IMHO with a cloistered group of people saying the status quo is just fine because it works for them exclusively.
- wheelerof4te 4y ago"The situation with Python on Debian has been pretty bad IMHO" The situation with anything has been pretty bad in Debian lately. I'm all for the minimalistic approach in regards to Python. It's Ok to provide only the packages needed by applications and the core system. For everything else, there's pip. EDIT: I've meant to say, there's pip inside a venv.
- qbasic_forever 4y agoI agree, the problem is if you just 'pip install foo' on Debian, like 99% of python docs and readmes say, it instantly fails. Worse yet if you think you should just elevate to root and force pip install to work you can potentially break the Python install. It's a nasty footgun.