All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: Chris PeBenito <pebenito@ieee.org>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH userspace] sepolicy: generate man pages in parallel
Date: Fri, 18 Oct 2019 11:22:01 +0200	[thread overview]
Message-ID: <CAFqZXNt5eYLMHCOuBBVjxRHSTG6H_FzNhHaHxza9kHC2yF+utA@mail.gmail.com> (raw)
In-Reply-To: <0a554b63-df42-fbc0-6877-f58c16156a9e@ieee.org>

On Fri, Oct 18, 2019 at 11:01 AM Chris PeBenito <pebenito@ieee.org> wrote:
> On 10/18/19 5:00 AM, Chris PeBenito wrote:
> > On 10/18/19 3:44 AM, Ondrej Mosnacek wrote:
> >> Since there are plans to support
> >> only Python 3 in 3.0+ this may not be an issue, but I could also add a
> >> few lines to fallback to sequential execution under Python 2 for the
> >> sake of compatibility. Would that be OK or should I not bother?
> >
> > Python 2 end of life is in less than 2 months.  Please don't add new
> > code only for Python 2 compatibility.
>
> I can't count.  It's a little over 2 months.  The point still stands :)

OK, I posted a v2 without the fallback.

-- 
Ondrej Mosnacek <omosnace at redhat dot com>
Software Engineer, Security Technologies
Red Hat, Inc.


      reply	other threads:[~2019-10-18  9:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-14  8:06 [PATCH userspace] sepolicy: generate man pages in parallel Ondrej Mosnacek
2019-10-17 17:14 ` Stephen Smalley
2019-10-18  7:44   ` Ondrej Mosnacek
2019-10-18  9:00     ` Chris PeBenito
2019-10-18  9:01       ` Chris PeBenito
2019-10-18  9:22         ` Ondrej Mosnacek [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=CAFqZXNt5eYLMHCOuBBVjxRHSTG6H_FzNhHaHxza9kHC2yF+utA@mail.gmail.com \
    --to=omosnace@redhat.com \
    --cc=pebenito@ieee.org \
    --cc=sds@tycho.nsa.gov \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.