From: Dirkjan Ochtman <djc@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python <gentoo-python@lists.gentoo.org>
Subject: Re: [gentoo-python] [RFC] Including (some) support for Tauthon
Date: Sat, 20 May 2017 11:26:21 +0200 [thread overview]
Message-ID: <CAKmKYaC6UPY4jCgj52HbL+L=QuBwBOAWo+Nu4b9ba4X8YPbBug@mail.gmail.com> (raw)
In-Reply-To: <1495221776.1965.5.camel@gentoo.org>
On Fri, May 19, 2017 at 9:22 PM, Michał Górny <mgorny@gentoo.org> wrote:
> Your thoughts?
I would say it's definitely too early to include support in the
project-maintained eclasses, especially assuming that you only
happened upon the fork. As you say, upstream's bus factor is not
inspiring confidence at this point, and until we see actual demand
from users, I don't think there's a point in even considering it.
Instead, we should consider removing Jython support!
Cheers,
Dirkjan
prev parent reply other threads:[~2017-05-20 9:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-19 19:22 [gentoo-python] [RFC] Including (some) support for Tauthon Michał Górny
2017-05-20 9:26 ` Dirkjan Ochtman [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='CAKmKYaC6UPY4jCgj52HbL+L=QuBwBOAWo+Nu4b9ba4X8YPbBug@mail.gmail.com' \
--to=djc@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.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