Alternatively, you can use tox -e mkvenv (without -pypi) to symlink your
local Qt install instead of installing PyQt in the virtualenv. However, unless
you have QtWebKit-NG or QtWebEngine available, qutebrowser will use the legacy
QtWebKit backend.

On Windows, run `tox -e mkvenv-win instead, however make sure that ONLY
Python3 is in your PATH before running tox.

This installs all needed Python dependencies in a .venv subfolder.

You can then create a simple wrapper script to start qutebrowser somewhere in
your $PATH (e.g. /usr/local/bin/qutebrowser or ~/bin/qutebrowser):

Updating

When you updated your local copy of the code (e.g. by pulling the git repo, or
extracting a new version), the virtualenv should automatically use the updated
code. However, if dependencies got added, this won’t be reflected in the
virtualenv. Thus it’s recommended to run the following command to recreate the
virtualenv: