From: Kacper Kowalik <xarthisius@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: [gentoo-python] Timeframe for supporting Python versions
Date: Mon, 30 Apr 2012 20:17:21 +0200 [thread overview]
Message-ID: <4F9ED731.2000407@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 868 bytes --]
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next reply other threads:[~2012-04-30 18:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:17 Kacper Kowalik [this message]
2012-04-30 20:13 ` [gentoo-python] Timeframe for supporting Python versions Dirkjan Ochtman
2012-04-30 21:01 ` Kacper Kowalik
2012-04-30 21:07 ` Johan Bergström
2012-05-02 13:52 ` Jesus Rivero (Neurogeek)
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=4F9ED731.2000407@gentoo.org \
--to=xarthisius@gentoo.org \
--cc=gentoo-python@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