On Sat, Apr 14, 2012 at 09:01:30PM +0200, Ralf Schmitt wrote: > Hi all, > > I've opened https://bugs.archlinux.org/task/28881 "meld uses wrong > shebang" some time ago. The description reads: > > ,---- > | meld uses "#! /usr/bin/env python2" as shebang. It should use "#! > | /usr/bin/python2". > `---- > > The bug has been closed as "Not a bug" and "Works fine as-is". I've > tried to reopen it, which has been denied, with the following comment: > > ,---- > | Reason for denial: > | Avoid using virtualenvs or install pygtk in them. > `---- > actually I originally switched to arch to have pygtk available for the python version in use. but this is just marginally related to your issue, which is IMO sufficiently invalidated by [1]. #!/usr/bin/env python2 and #!python2 in my experience have exactly the same effect, so all I can do is ask you what differences you found and then we could discuss how to work them around. A good proof of concept / educating experiment in that context would be to try running a python and pygtk fully in your home directory and without the repo versions present; if you have questions, please come back here with more factual questions. I'll gladly help you out. cheers! mar77i [1] http://www.python.org/dev/peps/pep-0397/
