You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pipsi makes installing python packages with global entry points painless. These are Python packages that expose an entry point through the command line such as Pygments.
If you are installing Python packages globally for cli access, you almost certainly want to use pipsi instead of running sudo pip .... so that you get
Isolated dependencies to guarantee no version conflicts
The ability to install packages globally without using sudo
The ability to uninstall a package and its dependencies without affecting other globally installed Python programs
pipsi is not meant for installing libraries that will be imported by other Python modules.
pipsi is a wrapper around virtualenv and pip which installs scripts provided by python packages into isolated virtualenvs so they do not pollute your system's Python packages.
pipsi installs each package into ~/.local/venvs/PKGNAME and then symlinks all new scripts into ~/.local/bin (these can be changed by PIPSI_HOME and PIPSI_BIN_DIR environment variables respectively).
Here is a tree view into the directory structure created by pipsi after installing pipsi and running pipsi install Pygments.
Compared to pip install --user each PKGNAME is installed into its own virtualenv, so you don't have to worry about different packages having conflicting dependencies. As long as ~/.local/bin is on your PATH, you can run any of these scripts directly.
Installing scripts from a package:
$ pipsi install Pygments
Installing scripts from a package using a particular version of python: