Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-python
Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-python@g.o
From: Kacper Kowalik <xarthisius@g.o>
Subject: Timeframe for supporting Python versions
Date: Mon, 30 Apr 2012 20:17:21 +0200
Hi all,
I'd like to bring a discussion that was started over irc for broader
audience. Namely:
1) how long are we supposed to keep old version of Python in Portage?
2) how many version should we actively maintained?

What came up:
 * python2.5 is no longer supported upstream since May 2011 and is first
candidate for purging
 * python3.2 supersedes python3.1 without introducing any obvious
incompatibilities (at least that's what they claim here[1])

What's worth noting is that upstream itself will provide/provides new
release cycle, introducing LTS version of python[2]. First proposal by
neurogeek, is that following pep0407 we should obsolete versions of
python 6 months after upstream ceases to support them. (+1 from me on that)

Cheers
Kacper

[1] http://www.python.org/dev/peps/pep-3003/
[2] http://www.python.org/dev/peps/pep-0407/

Attachment:
signature.asc (OpenPGP digital signature)
Replies:
Re: Timeframe for supporting Python versions
-- Dirkjan Ochtman
Navigation:
Lists: gentoo-python: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Testing dev-lang/python version bumps
Next by thread:
Re: Timeframe for supporting Python versions
Previous by date:
Re: Testing dev-lang/python version bumps
Next by date:
Re: Timeframe for supporting Python versions


Updated Jun 29, 2012

Summary: Archive of the gentoo-python mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.