On Thu, Apr 16, 2015 at 10:25 AM, Peter Maydell <[email protected]> wrote:
> There's no guarantee that python 2 is an executable named > "python". Commit e22723c8ee1 means the makefile always > runs this file via "$(PYTHON) test.py", so do we need the > #! line at all here? > I personally don't set PYTHON, so as-is I cannot use the makefile... I debated with myself adding: PYTHON ?= python2 to the makefile. But I did it the other way, which albeit not perfect, is an accepted idiom, that is used in the top level stg script itself. Or maybe I misunderstood your comment, and you just prefer being more specific, and would rather choose : #! /usr/bin/env python2 instead ? Please explain what is the problem with adding the shebang. -- Vincent Legoll
_______________________________________________ stgit-users mailing list [email protected] https://mail.gna.org/listinfo/stgit-users
