Use /usr/bin/env python instead of /usr/bin/python

The usage of /usr/bin/env ensures that the first interpreter
found in the environment's $PATH variable is used. This should
be preferred.

Change-Id: I4011ec477534f920092cc323a26e75ff26a90051
This commit is contained in:
Christian Berendt 2014-07-13 18:56:38 +02:00
parent 89dab30f3a
commit 8cbd60937d
6 changed files with 6 additions and 6 deletions

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Script to move bugs and blueprints to final release milestone page
#

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Idenpotent script to bulk-create milestones on Launchpad
#

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Script to determine version number from milestone codename
#

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Script to apply bulk changes to Launchpad bugs
#

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Script to upload an OpenStack release to Launchpad
#

View File

@ -1,4 +1,4 @@
#!/usr/bin/python
#!/usr/bin/env python
#
# Script to wait for a tarball to be generated in Jenkins
#