public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Aaron Bauman <bman@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] unsanctioned python 2.7 crusade
Date: Thu, 5 Dec 2019 09:40:50 -0500	[thread overview]
Message-ID: <20191205144050.GB5532@bubba.lan> (raw)
In-Reply-To: <20191205143416.GA3209@icarus>

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

On Thu, Dec 05, 2019 at 09:34:16AM -0500, William Breathitt Gray wrote:
> On Thu, Dec 05, 2019 at 09:24:26AM -0500, Rich Freeman wrote:
> > On Thu, Dec 5, 2019 at 8:59 AM Jason A. Donenfeld <zx2c4@gentoo.org> wrote:
> > >
> > > It's quite another to mask random packages that have USE flags to
> > > optionally support whatever python 2.7 library. If you're going to
> > > last rites these, talk with the maintainer first, and only then, send
> > > emails one at a time. Doing that en masse isn't appropriate.
> > 
> > ++ - I have no idea if that happened.  For anything USE-controlled it
> > would make more sense to file a bug or mask the package-flag combo
> > itself.
> > 
> > >
> > > On another topic, I'd prefer for python 2.7 not to be removed from
> > > gentoo. Tons of code still uses it.
> > >
> > 
> > I'm sure a million people would share that preference.  I'm not sure
> > what the upstream/security status is of 2.7.  Obviously to keep it
> > around it would need to be reasonably secure, and somebody within
> > Gentoo would have to want to maintain it.  That's basically the
> > criteria for keeping anything like this around.  If somebody stepped
> > up and said "I'm maintaining 2.7 and here is why it will remain
> > secure..." I doubt they'd get a lot of resistance.
> > 
> > -- 
> > Rich
> 
> If Python 2.7 is EOL upstream then it sounds like upstream will not be
> maintaining it any longer; i.e. no more bug fixes nor support. That
> means Gentoo would have to maintain its own Python 2.7 fork if it's to
> remain in the repository. Naturally, maintaining a Python fork is not
> something the Gentoo team is ready to do, so it makes sense to remove
> Python 2.7 now that the EOL date is approaching.
> 
> Besides, the Python 2.7 EOL date has been known since 2015, so those
> python 2-only packages will have had at least 5 years to migrate to
> Python 3.
> 
> William Breathitt Gray
> 

Wonderful response, William.

For the others who are seeking a quick "why? how? when? what?" there are these
links:

https://pythonclock.org/

https://python3statement.org/ <--- This is a fun one. All the naysayers need to
go yell at the projects too!

-- 
Cheers,
Aaron

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-12-05 14:40 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 [this message]
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=20191205144050.GB5532@bubba.lan \
    --to=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