From: Kent Fredric <kentnl@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade
Date: Fri, 6 Dec 2019 19:53:13 +1300 [thread overview]
Message-ID: <20191206195313.6c75ab2e@katipo2.lan> (raw)
In-Reply-To: <20191205144050.GB5532@bubba.lan>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
On Thu, 5 Dec 2019 09:40:50 -0500
Aaron Bauman <bman@gentoo.org> wrote:
> Wonderful response, William.
Just because its EOL, doesn't mean it stops working.
It just means *support* for defects and security problems is dropped.
It doesn't prevent us from:
a) vendor patching bugs
b) vendor patching security issues
So as much as I'm fervently annoyed by needing python 2 on my system
and want to get rid of it post-haste, I too think this move is too
aggressive.
It seems more sensible to me to remove things on the basis of a
*credible problem*, not on the basis of a conjecture that one could
appear in the future.
I'm not averse to change, I just understand for change to be executed
successfully, gradual and careful adjustments have to be made.
Though I deeply suspect once package.deprecated becomes a thing we can use,
we can relegate py2-only stuff there.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-06 6:53 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
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 [this message]
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=20191206195313.6c75ab2e@katipo2.lan \
--to=kentnl@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