From: Nick T. <pro...@gm...> - 2014-08-05 00:44:43
|
A common stumbling block that I hit when using Diffuse and Python virtualenvs is that because the shebang of Diffuse is "#!/usr/bin/env python", it grabs my virtualenv, which inevitably doesn't have PyGTK installed then crashes. I've had to explain to another couple users that, "yeah, you need to execute it from outside your virtual environment". By way of comparison, hg always uses the system Python ("#! /usr/bin/python"). I class Diffuse with Mercurial, machine-specific programs that should use local system resources, not something that should ever change based on the context or environment in which I run it. Can this be altered or is there a deeper purpose to using the environment's Python? I'd submit a patch but it'd be a bit of a joke; deleting 4 characters ;) Cheers, Nick |