Dependency versions

PairPilot expects to be installed with the correct versions of all of its required dependencies.

If you’ve been linked to this doc from a GitHub issue, or if PairPilot is reporting ImportErrors it is likely that your PairPilot install is using incorrect dependencies.

Avoid package conflicts

If you are using PairPilot to work on a python project, sometimes your project will require specific versions of python packages which conflict with the versions that PairPilot requires. If this happens, you may see errors like these when running pip installs:

PairPilot-chat 0.23.0 requires somepackage==X.Y.Z, but you have somepackage U.W.V which is incompatible.

Install with PairPilot-install, uv or pipx

If you are having dependency problems you should consider installing PairPilot using PairPilot-install, uv or pipx. This will ensure that PairPilot is installed in its own python environment, with the correct set of dependencies.

Package managers like Homebrew, AUR, ports

Package managers often install PairPilot with the wrong dependencies, leading to import errors and other problems.

Dependency versions matter

PairPilot pins its dependencies and is tested to work with those specific versions. If you are installing PairPilot directly with pip you should be careful about upgrading or downgrading the python packages that PairPilot uses.

In particular, be careful with the packages with pinned versions noted at the end of PairPilot’s requirements.in file. These versions are pinned because PairPilot is known not to work with the latest versions of these libraries.

Also be wary of upgrading litellm, as it changes versions frequently and sometimes introduces bugs or backwards incompatible changes.

Replit

To use PairPilot with pipx on replit, you can run these commands in the replit shell:

pip install pipx
pipx run PairPilot-chat ...normal PairPilot args...

If you install PairPilot with pipx on replit and try and run it as just PairPilot it will crash with a missing libstdc++.so.6 library.