The post is about out of the box functionality. Requiring a user to also install some system package kinda defeats the purpose here. Plus it's usually not the same version of the library that was expected by the developer of the script.

Even used in a venv pip creates a mess as people start creating ad hoc environments and don't really know how to recreate them (cause of many "works for me" type problems). I always advise people to take the extra step of adding a new dependency to pyproject.toml or requirements.txt and then doing `pip install -e .` or `pip install -r requirements.txt`.

> it's usually not the same version of the library that was expected by the developer of the script

If the developer of the script is targeting that platform, it is exactly the expected version.

Perhaps you should stop using libraries that break API compatibility very often, since it's an indicator of low skill of the authors.