Sharing scripts that require a virtualenv to be activated

Question

I have virtualenv and virtualenvwrapper installed on a shared Linux server with default settings (virtualenvs are in ~/.virtualenvs). I have several Python scripts that can onl

Answer 1

I would vote for adding a shebang line in scriptname pointing to the correct virtualenv python. You just tell your users the full path to scriptname (or put it in their PATH), and they don't even need to know it is a Python script.

If your users are programmers, then I don't see why you wouldn't want them to know/learn about virtualenv.

Answer 2

Use the following magic(5) at the start of the script.

#!/usr/bin/env python

Change which virtualenv is active and it'll use the python from that virtualenv. Deactivate the virtualenv, it still runs.

Answer 3

If it's only on one server, then flexibility is irrelevant. Modify the shebang. If you're worried about that, make a packaged, installed copy on the dev server that doesn't use the virtualenv. Once it's out of develepment, whether that's for local users or users in guatemala, virtualenv is no longer the right tool.