public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Last rites: dev-python/* leaf packages
Date: Wed, 4 Dec 2019 21:06:31 -0600	[thread overview]
Message-ID: <20191205030631.GA13848@linux1.home> (raw)
In-Reply-To: <9ec9b423-0e6f-fb2a-4a1b-832187735719@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 649 bytes --]

On Thu, Dec 05, 2019 at 03:56:05AM +0100, Thomas Deutschmann wrote:
> Hi,
> 
> On 2019-12-05 01:15, Aaron Bauman wrote:
> > * Removal in 30 days
> 
> Why? I understand that Py2 will reach EOL upstream status but we all
> know that Py2 will *not* disappear and stop working in 26 days...
> 
> There's no reason to mask/remove currently known working software.
> 
> net-nntp/sabnzbd is a perfect example. Up to date in repository and working.

Are you volunteering to maintain it or open an upstream bug and askthem
to move to py3?

I tend to think that we should either get py2 only software to move to
py3 or remove it.

William

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2019-12-05  3:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  0:15 [gentoo-dev] Last rites: dev-python/* leaf packages Aaron Bauman
2019-12-05  0:28 ` Michael 'veremitz' Everitt
2019-12-05  1:00   ` Aaron Bauman
2019-12-05  1:22 ` Robert Förster
2019-12-05  2:56 ` Thomas Deutschmann
2019-12-05  3:06   ` William Hubbs [this message]
2019-12-05  3:20     ` Thomas Deutschmann
2019-12-05  7:24   ` Michał Górny
2019-12-05  6:55 ` Poncho
2019-12-05 10:00 ` Tobias Klausmann
2019-12-05 11:38 ` Gerion Entrup
2019-12-05 12:28 ` Alexis Ballier

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=20191205030631.GA13848@linux1.home \
    --to=williamh@gentoo.org \
    --cc=gentoo-dev@lists.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