From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2
Date: Tue, 2 Jun 2015 10:43:18 -0400 [thread overview]
Message-ID: <20150602144318.GA23039@vapier> (raw)
In-Reply-To: <556D35E3.20303@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On 02 Jun 2015 06:49, Alexander Berntsen wrote:
> On 02/06/15 06:42, Mike Frysinger wrote:
> > the portage ebuild dropped support:
> > python 3.1: 21 months ago
> > python 2.6: 10 months ago
> > python 3.2: 8 weeks ago
> >
> > the python team itself no longer supports these versions either and
> > it's not possible to install other modules using them. they're
> > already forcing you to pick 2.7 or 3.3+.
> You make a compelling case here.
>
> > plus, i'm not talking about changing existing releases, just new
> > ones, which means it's going to be a while before people are
> > completely impacted.
> I realise that. Anything else would be stupid.
>
> > at some point we have to move forward and the shims for 2.6/3.1/3.2
> > are holding us back now. 2.6 is obvious enough, but 3.1 & 3.2 are a
> > pain due to the unicode differences. conversely, py2.7 and py3.3+
> > have the same unicode literal format.
> I agree on all points.
>
>
> So I think this patch would be fine to merge. I'd like Brian to chime in, but I'm a tentative +1.
<dol-sen> but yeah, I don't see a problem in dropping them
<zmedico> yeah
<dol-sen> especially since gkeys is not 3.2 capable
<dol-sen> and I'm starting to integrate it in portage
<zmedico> those pythons are ancient
-mike
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-06-02 14:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-30 14:58 [gentoo-portage-dev] [PATCH] officially drop support for python 2.6, 3.1, and 3.2 Mike Frysinger
2015-06-01 21:16 ` Alexander Berntsen
2015-06-02 4:42 ` Mike Frysinger
2015-06-02 4:49 ` Alexander Berntsen
2015-06-02 14:43 ` Mike Frysinger [this message]
2015-06-02 14:49 ` Alexander Berntsen
2015-06-02 15:33 ` Mike Frysinger
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=20150602144318.GA23039@vapier \
--to=vapier@gentoo.org \
--cc=gentoo-portage-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