chore: replace pip3 install with pipx install #84
+2
−2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using pip3 install to install PyPI packages can cause headache, or worse, break system packages on Linux distributions.
Vladimyr did a good write-up about it on our Matrix chat:
https://matrix.to/#/!HiSKnvVsCpWxkTWWMC:gitter.im/$_8RsjYQBQIIcOGfhrJNm2fvex3O9tWnn0lhIb8riX5M?via=gitter.im&via=matrix.org&via=one.ems.host
Debian would also yell at me if I tried to follow those instructions:
pip3 install tldrMeanwhile, I'd recommend suggesting
pipxinstead ofpip3.https://github.com/pypa/pipx
This creates a venv behind the scenes, isolating the package and it's dependencies from other system-wide packages, so there's no risk of conflict. In Python-land, it's also a common way to install binaries anyway, for example Poetry (a very popular package/project manager for Python) also recommends installing it with pipx.