Linux

Have you tried what the message tells you?

A good amount of distros actively have this functionality. To avoid breaking system packages, you can install the distro package for the given module or as the error recommends: use a venv for the given project.

As to why many guides don't include it, I suspect as typical for many Linux-centric articles: they weren't been written by knowledgeable individuals or just in general are writing with knowledge that is often 5+ years out of date.

The error message is very detailed and there is nothing to add to it.

If you want to install an application/CLI tool, use pipx or your system package manager. If you want to install a library, use a virtual environment (e.g. by using python -m venv) or your system package manager.

I think the error is quite verbose and tells you everything you need to know.

Generally, do not install packages outside of a virtual environment unless you know what you're doing. Given the option, use your package manager version of the same package. Outside of that, use your python environment manager of choice to install stuff. There are lots of options: conda, uv, venv, virtualenv, pipenv, etc.

The error exists to warn you that you could potentially break critical system installed packages by installing other things at a user or system level with pip.

It's mostly Debian-focused, but you should probably use venvs. They allow you to have different versions of Python packages for different applications. I especially like it when using it in combination with pythonz for applications that require a different version than the system Python.

I find they prevent the system Python from being a complete pile of anarchy.

Like others have said, the error tells you everything you need to know.

In some Linux distributions it blocks you from installing system packages via pip, often there are then packages which can be installed via your distros package manager.

With arch for example:

sudo pacman -S python-'package'

Or, as others mentioned using venv.

I always create a virtual environment for each project I run like that. This way you can have your own versions of packages for each project without them interfearing with each other. This is also what the error message sugests in the beginning, so if you have the time I would investigate it and learn about it: https://python.land/virtual-environments/virtualenv

If you want access to it at system-level, you can use pip install --user .... If you run scripts as your user it'll be as if it was installed as a system package.

Only use that if it's something you use to manage your system. If you're using this as a development environment, use venvs.

If you're tired of python's and venv issues, give miniconda a try. It solved most of my issues with dependencies and different python version in scripts.

It's probably a skill issue regarding to pip/pipx/venv... But miniconda really made everything easier.

Welcome to Debian! Listen to @treadful@lemmy.zip, that's the easy advice.