FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > ArchLinux > ArchLinux General Discussion

 
 
LinkBack Thread Tools
 
Old 04-14-2012, 07:01 PM
Ralf Schmitt
 
Default shebang for python scripts

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.
`----

The above is not a "reason for denial" but a workaround, and strictly
speaking a bad workaround. A good workaround would be to "put no custom
paths in front of the archlinux provided paths in PATH".

I really do think the user should be able to install custom python
versions in his home directory (be it through virtualenv or by compiling
from sources) and put them in front of PATH without breaking random
python scripts in /usr/bin.

Generally I'm quite impressed by the good decisions and great work being
made by the archlinux developers, but in this case I'm deeply
disappointed and can't really understand the rationale behind this
decision.

Can someone explain it to me please? Please also explain why some
programs do have a /usr/bin/python2 shebang and some don't!

--
Cheers
Ralf
 

Thread Tools




All times are GMT. The time now is 05:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org