public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Rich Freeman <rich0@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Cc: Aaron Bauman <bman@gentoo.org>
Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade
Date: Thu, 5 Dec 2019 08:55:56 -0500	[thread overview]
Message-ID: <CAGfcS_=mLOmKScFumzfQ5T2jNOFRnRB9=L3H0e040AiuXExt8g@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qRcahsTHju527n0Figd7o8d7-tS_ZmdFBgUBALms5xAg@mail.gmail.com>

On Thu, Dec 5, 2019 at 8:42 AM Jason A. Donenfeld <zx2c4@gentoo.org> wrote:
>
> Hi,
>
> Aaron has marked tons of important and useful Python 2.7 packages for removal:
>
> Can we not do this prematurely? I've revered this commit until such a
> thing an be appropriately agreed upon.

Might make sense to wait to mask them at the same time as masking
python 2.7 itself?  Maybe file a bug if not already done to make
maintainers aware that this is coming?

I assume the python team is the one deciding when python 2.7 has to go
(after all, who else is going to maintain it?).  The fact that this is
about a month off did come up in another recent thread but I don't
think it was intended as a formal announcement.

-- 
Rich


  reply	other threads:[~2019-12-05 13:56 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 13:42 [gentoo-dev] unsanctioned python 2.7 crusade Jason A. Donenfeld
2019-12-05 13:55 ` Rich Freeman [this message]
2019-12-05 13:59   ` Jason A. Donenfeld
2019-12-05 14:24     ` Rich Freeman
2019-12-05 14:34       ` William Breathitt Gray
2019-12-05 14:40         ` Aaron Bauman
2019-12-06  6:53           ` Kent Fredric
2020-01-12 22:07       ` Joshua Kinard
2020-01-12 22:17         ` David Seifert
2020-01-12 22:29           ` Joshua Kinard
2020-01-12 22:32         ` Andreas Sturmlechner
2020-01-12 22:43           ` Joshua Kinard
2020-01-12 22:46             ` David Seifert
2020-01-12 22:55               ` Joshua Kinard
2020-01-12 23:17                 ` David Seifert
2020-01-13  0:21                   ` William Hubbs
2020-01-13  0:44                     ` Joshua Kinard
2020-01-13  7:22                       ` Andreas Sturmlechner
2020-01-13  6:52         ` Michał Górny
2020-01-14  6:45           ` Joshua Kinard
2019-12-05 20:31     ` David Seifert
2019-12-05 20:56       ` Thomas Deutschmann
2019-12-05 22:23         ` David Seifert
2019-12-05 22:41           ` Rich Freeman
2019-12-06  8:11           ` Mart Raudsepp
2019-12-06 10:48             ` David Seifert
2019-12-06 13:06             ` Thomas Deutschmann
2019-12-06 13:52               ` Rich Freeman
2019-12-06 15:48                 ` Mike Gilbert
2019-12-06 16:12                   ` Thomas Deutschmann
2019-12-06 16:44                     ` Mike Gilbert
2019-12-06 19:47                       ` Thomas Deutschmann
2019-12-06 20:10                         ` Andreas Sturmlechner
2019-12-06 20:28                           ` Thomas Deutschmann
2019-12-08 10:28                             ` Alexis Ballier
2019-12-06 20:30                           ` Michael 'veremitz' Everitt
2019-12-07  8:04                           ` Kent Fredric
2019-12-06 16:35               ` Mart Raudsepp
2019-12-06 16:43                 ` Thomas Deutschmann
2019-12-05 14:36 ` Aaron Bauman
2019-12-05 16:03 ` Andreas K. Huettel

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='CAGfcS_=mLOmKScFumzfQ5T2jNOFRnRB9=L3H0e040AiuXExt8g@mail.gmail.com' \
    --to=rich0@gentoo.org \
    --cc=bman@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