dh-virtualenv

Our continuous integration server (Jenkins) runs dh-virtualenv to build the package, and uses Python’s wheel cache to avoid re-building dependencies.

We use dh-virtualenv and it's working out pretty well for us so far.

We have no problems with pyenv and pip locally, and dh-virtualenv in production.

We do something similar at embedly, except instead of dh-virtualenv we have our own homegrown solution.

I wonder if you could combine it with the sandboxing that dh-virtualenv provides to get the best of both worlds?

Some build systems (eg Debian + python + dh-virtualenv) like to produce very long paths, and I'd be inclined to just let them.

I had never heard of dh-virtualenv but will be looking into it.

I wish I new about dh-virtualenv before we created it.

> Building with dh-virtualenv simply creates a debian package that includes a virtualenv, along with any dependencies listed in the requirements.txt file.

At least once I've deployed via dh-virtualenv and rpmvenv, pyinstaller, cx_freeze, or tested for compatibility with the system Python if I could control for the client machines.

I want it to go one level deeper (we use dh-virtualenv to put several Python packages into one Debian package, but that's only done in a very small part of the company).

How does this compare with the "dh-virtualenv" tool recommended by the article?