From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: [PATCH 1/3] Always use /usr/bin/python3 in Python scripts
Date: Thu, 21 Feb 2019 21:17:18 +0100 [thread overview]
Message-ID: <CAJfZ7=kL2D5K9J-+C8bK4KqeEV4qQed745AMrAZ+BhH=ODiihQ@mail.gmail.com> (raw)
In-Reply-To: <20190220160446.23150-2-plautrba@redhat.com>
On Wed, Feb 20, 2019 at 5:04 PM Petr Lautrbach <plautrba@redhat.com> wrote:
>
> Signed-off-by: Petr Lautrbach <plautrba@redhat.com>
For the 3 patches:
Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
> ---
> dbus/selinux_server.py | 2 +-
> libsemanage/utils/semanage_migrate_store | 2 +-
> mcstrans/share/util/mlscolor-test | 2 +-
> mcstrans/share/util/mlstrans-test | 2 +-
> python/semanage/semanage | 2 +-
> sandbox/start | 2 +-
> 6 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/dbus/selinux_server.py b/dbus/selinux_server.py
> index 6e380e58..98ab53dd 100644
> --- a/dbus/selinux_server.py
> +++ b/dbus/selinux_server.py
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python
> +#!/usr/bin/python3
>
> import dbus
> import dbus.service
> diff --git a/libsemanage/utils/semanage_migrate_store b/libsemanage/utils/semanage_migrate_store
> index 018b1a3e..c6caf3bf 100755
> --- a/libsemanage/utils/semanage_migrate_store
> +++ b/libsemanage/utils/semanage_migrate_store
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python -E
> +#!/usr/bin/python3 -E
>
>
> from __future__ import print_function
> diff --git a/mcstrans/share/util/mlscolor-test b/mcstrans/share/util/mlscolor-test
> index 03fc4be4..240e996d 100644
> --- a/mcstrans/share/util/mlscolor-test
> +++ b/mcstrans/share/util/mlscolor-test
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python -E
> +#!/usr/bin/python3 -E
> import sys
> import selinux
>
> diff --git a/mcstrans/share/util/mlstrans-test b/mcstrans/share/util/mlstrans-test
> index c026d00e..085fa82d 100644
> --- a/mcstrans/share/util/mlstrans-test
> +++ b/mcstrans/share/util/mlstrans-test
> @@ -1,4 +1,4 @@
> -#!/usr/bin/python -E
> +#!/usr/bin/python3 -E
> import sys
> import selinux
>
> diff --git a/python/semanage/semanage b/python/semanage/semanage
> index d6d68248..144cc000 100644
> --- a/python/semanage/semanage
> +++ b/python/semanage/semanage
> @@ -1,4 +1,4 @@
> -#! /usr/bin/python3 -Es
> +#!/usr/bin/python3 -Es
> # Copyright (C) 2012-2013 Red Hat
> # AUTHOR: Miroslav Grepl <mgrepl@redhat.com>
> # AUTHOR: David Quigley <selinux@davequigley.com>
> diff --git a/sandbox/start b/sandbox/start
> index 7f83532f..4ed3cb5c 100644
> --- a/sandbox/start
> +++ b/sandbox/start
> @@ -1,4 +1,4 @@
> -#! /usr/bin/python -Es
> +#!/usr/bin/python3 -Es
> try:
> from subprocess import getstatusoutput
> except ImportError:
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-02-21 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-20 16:04 [RFC] Switch to Python 3 by default Petr Lautrbach
2019-02-20 16:04 ` [PATCH 1/3] Always use /usr/bin/python3 in Python scripts Petr Lautrbach
2019-02-21 20:17 ` Nicolas Iooss [this message]
2019-02-26 13:21 ` Petr Lautrbach
2019-02-20 16:04 ` [PATCH 2/3] Switch to python3 by default Petr Lautrbach
2019-02-20 16:04 ` [PATCH 3/3] README: Update Fedora python 3 dependencies Petr Lautrbach
2019-02-20 21:17 ` [RFC] Switch to Python 3 by default Stephen Smalley
2019-02-21 19:00 ` Nicolas Iooss
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='CAJfZ7=kL2D5K9J-+C8bK4KqeEV4qQed745AMrAZ+BhH=ODiihQ@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=plautrba@redhat.com \
--cc=selinux@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;
as well as URLs for NNTP newsgroup(s).