From: Brian Dolbec <dolsen@gentoo.org>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-python@lists.gentoo.org, python@gentoo.org
Subject: Re: [gentoo-python] Killing CPython 2.5, 3.1 and PyPy 1.9
Date: Sun, 04 Aug 2013 07:03:59 -0700 [thread overview]
Message-ID: <1375625039.3583.19.camel@big_daddy.dol-sen.ca> (raw)
In-Reply-To: <20130804110158.5c28d9d4@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 1284 bytes --]
On Sun, 2013-08-04 at 11:01 +0200, Michał Górny wrote:
> Hello, folks.
>
> I think we should start dropping support for really old
> implementations. PyPy 1.9 probably has most of the agreement already.
>
> For CPython 2.5, it's mostly virtual/pil giving me creeps. Since old
> imaging does not support 3.3 and PIL does not support 2.5, there is no
> way all impls could be satisfied with the virtual. So I dropped 2.5
> from my PYTHON_TARGETS a while ago and I don't test packages against it
> anymore.
>
I had to drop 2.5 from my targets as well, pkgs are starting to fail
with it as more are dropping 2.5 support. the current layman-2.0.0
supports 2.5 which was used by some embedded devs, but it will be the
last one I support with layman. Next minor version will be 2.6+.
Yeah time to drop 2.5
> For CPython 3.1, I guess nobody really cares about it. At least I don't
> recall a single reason to keep it.
>
Yeah, nuke 3.1 it has compatibility issues with other 2.x and 3.x
releases. Several app-portage pkgs had to drop support for 3.1 due to
that. Upstream even dropped support for it.
> What do you think?
>
> (of course, we'd have to ensure updated PYTHON_TARGETS prior to killing)
>
--
Brian Dolbec <dolsen@gentoo.org>
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
prev parent reply other threads:[~2013-08-04 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-04 9:01 [gentoo-python] Killing CPython 2.5, 3.1 and PyPy 1.9 Michał Górny
2013-08-04 11:27 ` [gentoo-python] " Marien Zwart
2013-08-05 3:33 ` Arfrever Frehtes Taifersar Arahesis
2013-08-05 10:10 ` Marien Zwart
2013-08-04 14:03 ` Brian Dolbec [this message]
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=1375625039.3583.19.camel@big_daddy.dol-sen.ca \
--to=dolsen@gentoo.org \
--cc=gentoo-python@lists.gentoo.org \
--cc=mgorny@gentoo.org \
--cc=python@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