selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Petr Lautrbach <plautrba@redhat.com>
Cc: selinux@vger.kernel.org
Subject: Re: [RFC] Switch to Python 3 by default
Date: Thu, 21 Feb 2019 20:00:36 +0100	[thread overview]
Message-ID: <CAJfZ7=mFhPWSOmpaiBHVpYOeKhCUH=qVro=X=1d=yLsQOi_wfQ@mail.gmail.com> (raw)
In-Reply-To: <CAB9W1A3GWkg+hKZVeyH31Trfiz3eiaNAXf3FEH1z=roDoBiqqw@mail.gmail.com>

On Wed, Feb 20, 2019 at 10:18 PM Stephen Smalley
<stephen.smalley@gmail.com> wrote:
>
> On Wed, Feb 20, 2019 at 11:05 AM Petr Lautrbach <plautrba@redhat.com> wrote:
> >
> >
> > Default instalation seems to be inconsistent a little when PYTHON
> > variable is not used during build. Python 2 versions of selinux and
> > semanage modules are built and installed, but /usr/sbin/semanage and
> > other tools are already changed to use /usr/bin/python3.
> >
> > I'd like to propose to change to Python 3 by default and leave it on a
> > maintainer to use PYTHON=/usr/bin/python2 when they doesn't have Python
> > 3 available. They would also need to change shebangs of some tools, but
> > this is the same situation as used to be when default was Python 2 and
> > maintainers needed to change shebangs to /usr/bin/python3.
> >
> > Do you have any objections?
>
> Sounds good to me.

I agree.

Cheers,
Nicolas


      reply	other threads:[~2019-02-21 19:00 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
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 [this message]

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=mFhPWSOmpaiBHVpYOeKhCUH=qVro=X=1d=yLsQOi_wfQ@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).