From: Don Zickus <dzickus@redhat.com>
To: linux-kernel@vger.kernel.org
Subject: Fwd: [scripts] python: change scripts to use system python instead of env
Date: Tue, 26 Jan 2010 17:20:41 -0500 [thread overview]
Message-ID: <20100126222041.GR4472@redhat.com> (raw)
Doh. Typo in the To: field
----- Forwarded message from Don Zickus <dzickus@redhat.com> -----
Date: Fri, 22 Jan 2010 16:32:10 -0500
From: Don Zickus <dzickus@redhat.com>
To: lkml@vger.kernel.org
Cc: akpm@linux-foundation.org, tglx@linutronix.de, tony.luck@intel.com,
kmcmartin@redhat.com, Don Zickus <dzickus@redhat.com>
Subject: [scripts] python: change scripts to use system python instead of env
Message-Id: <1264195930-15815-1-git-send-email-dzickus@redhat.com>
Just a small change to a couple of scripts to go from
#!/usr/bin/env python
to
#!/usr/bin/python
This shouldn't effect anyone, unless they don't install python there.
In preparation for python3, Fedora is doing a big push to change the scripts
to use the system python. This allows developers to put the python3 in
their path without fear of breaking existing scripts.
Now I am pretty sure anyone using python3 for testing purposes will probably
not run any of the scripts I changed, but Fedora has this automated tool
that checks for this stuff so I thought I would try to push it upstream.
Signed-off-by: Don Zickus <dzickus@redhat.com>
--
I don't do enough python to defend this change to much other than it seems
to make sense.
---
arch/ia64/scripts/unwcheck.py | 2 +-
scripts/rt-tester/rt-tester.py | 2 +-
scripts/show_delta | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/ia64/scripts/unwcheck.py b/arch/ia64/scripts/unwcheck.py
index c278498..2bfd941 100644
--- a/arch/ia64/scripts/unwcheck.py
+++ b/arch/ia64/scripts/unwcheck.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/python
#
# Usage: unwcheck.py FILE
#
diff --git a/scripts/rt-tester/rt-tester.py b/scripts/rt-tester/rt-tester.py
index 4c79660..44423b4 100644
--- a/scripts/rt-tester/rt-tester.py
+++ b/scripts/rt-tester/rt-tester.py
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/python
#
# rt-mutex tester
#
diff --git a/scripts/show_delta b/scripts/show_delta
index 48a706a..17df305 100755
--- a/scripts/show_delta
+++ b/scripts/show_delta
@@ -1,4 +1,4 @@
-#!/usr/bin/env python
+#!/usr/bin/python
#
# show_deltas: Read list of printk messages instrumented with
# time data, and format with time deltas.
--
1.6.6.83.gc9a2
----- End forwarded message -----
next reply other threads:[~2010-01-26 22:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 22:20 Don Zickus [this message]
2010-01-27 2:34 ` [scripts] python: change scripts to use system python instead of env Américo Wang
2010-01-28 20:21 ` Jarod Wilson
2010-01-29 11:50 ` Michal Marek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100126222041.GR4472@redhat.com \
--to=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox