virtualenv

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

Our deployment system handles running django migrations by deploying to a new folder/virtualenv, running the migrations, then switching over symlinks.

What was wrong with Python packaging that conda needed to replace it entirely (including virtualenv)?

For example, my python virtualenv prompt gets broken into two lines, both with a mark, which causes line lengths to misbehave too sometimes.

For me, there's virtualenv and rvm that both mess with shell stuff deeply enough to where running them in fish can be tricky.

That leads naturally to the fat jar/virtualenv/static binary approach with manually managed dependencies which gives you isolation between applications, and all the associated costs.

It also packs up a complete virtualenv, and installs the build time OS dependencies on the Docker machine where it builds on when needed.

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

You can use virtualenv to address these and related issues.

I typically rec installing virtualenv systemwide, if a reasonable version is available by package, and managing per-app dependencies in a requirements.txt that's platform agnostic.

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

Debian stable includes pip and virtualenv.

For example, one tool requires me to "source environment.sh" (similar to virtualenv) and this cannot be done in fish.

You do not need to remember a special "deactivate" command like with virtualenv.

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

If you're a virtualenv user, I use this one-liner to start load a virtualenv named after the current directory: alias v='workon "${PWD##*/}"' Also, I really like the -p flag of mkdir (creating child directories as needed, without failing if one doesn't exist) alias mkdir='mkdir -p' # i.e.