diffuse-users Mailing List for Diffuse

Nick,

The "#!/usr/bin/env python" bit was intended to help make Diffuse a bit more portable as Python is normally located at /usr/local/bin/python on some platforms.  This should not be needed any more as the install.py script will update the path as needed during installation or building a package.  It should be safe^{TM} to change it.


Cheers,
Derrick



________________________________
 From: Nick Timkovich <pro...@gm...>
To: dif...@li... 
Sent: Monday, 4 August 2014, 20:44
Subject: [Diffuse-users] Using system Python
 


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
------------------------------------------------------------------------------
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
_______________________________________________
Diffuse-users mailing list
Dif...@li...
https://lists.sourceforge.net/lists/listinfo/diffuse-users

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