[gentoo-python] Killing CPython 2.5, 3.1 and PyPy 1.9

[gentoo-python] Killing CPython 2.5, 3.1 and PyPy 1.9

[Michał Górny]

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

Hello, folks.

PyPy 2.1 is out, we expected PyPy3 2.1 and CPython 3.4 at some point.
Then Jython 2.7 (maybe sometime near CPython 3.6).

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.

For CPython 3.1, I guess nobody really cares about it. At least I don't
recall a single reason to keep it.

What do you think?

(of course, we'd have to ensure updated PYTHON_TARGETS prior to killing)

-- 
Best regards,
Michał Górny

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

[gentoo-python] Re: Killing CPython 2.5, 3.1 and PyPy 1.9

[Marien Zwart]

On Sun, Aug 4, 2013 at 7:01 PM, Michał Górny <mgorny@gentoo.org> wrote:
> What do you think?

+1 for dropping all three. PyPy is still enough of a moving target
keeping old versions around is IMO not worth it. I'd similarly not
expect too many people to care about Python 3 before 3.2 (3.2 is the
special long-term-supported ABI release though, so that one should
probably stick around).

There's probably still some people using 2.5 but at this point I doubt
virtual/imaging is the only thing in the tree that'll break/require
extra maintenance to work with 2.5. So yeah, drop them from the main
tree. If people still need them, they can use an overlay / old ebuilds
from CVS.
-- 

Marien Zwart (marienz)

Re: [gentoo-python] Killing CPython 2.5, 3.1 and PyPy 1.9

[Brian Dolbec]

[-- 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 --]

Re: [gentoo-python] Re: Killing CPython 2.5, 3.1 and PyPy 1.9

[Arfrever Frehtes Taifersar Arahesis]

[-- Attachment #1: Type: Text/Plain, Size: 1243 bytes --]

2013-08-04 13:27 Marien Zwart napisał(a):
> 3.2 is the special long-term-supported ABI release

No. Each branch X.Y (except 3.0) has general bug fix support until a X.Y.* release some time relatively
shortly before or after release of X.(Y+1).0 and security fix support for 5 years after release of X.Y.0.

http://www.python.org/download/releases/3.1/   "Python 3.1 final was released on June 27th, 2009."
http://www.python.org/download/releases/3.1.4/ "Python 3.1.4 was released on June 11th, 2011."
http://www.python.org/download/releases/3.2/   "Python 3.2 was released on February 20th, 2011."
http://www.python.org/download/releases/3.2.5/ "Python 3.2.5 was released on May 15th, 2013.
http://www.python.org/download/releases/3.3.0/ "Python 3.3.0 was released on September 29th, 2012."
http://www.python.org/dev/peps/pep-0429/       "3.4.0 final: February 23, 2014"

Python 3.1 was receiving general bug fixes until 2011-06-11 and receives security fixes until 2014-06-27.
Python 3.2 was receiving general bug fixes until 2013-05-15 and receives security fixes until 2016-02-20.
Python 3.3 receives general bug fixes until 2014-*-* and receives security fixes until 2017-09-29.

--
Arfrever Frehtes Taifersar Arahesis

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

Re: [gentoo-python] Re: Killing CPython 2.5, 3.1 and PyPy 1.9

[Marien Zwart]

On Mon, Aug 5, 2013 at 1:33 PM, Arfrever Frehtes Taifersar Arahesis
<arfrever.fta@gmail.com> wrote:
> 2013-08-04 13:27 Marien Zwart napisał(a):
>> 3.2 is the special long-term-supported ABI release
>
> No. Each branch X.Y (except 3.0) has general bug fix support until a X.Y.* release some time relatively
> shortly before or after release of X.(Y+1).0 and security fix support for 5 years after release of X.Y.0.

I was (rather imprecisely) referring to PEP 384. Although there is
Py_LIMITED_API I could see people wanting to actually build against
3.2 to make sure code trying to make use of this additional backwards
compatibility actually is backwards compatible.
-- 

Marien Zwart (marienz)