From: Kacper Kowalik <xarthisius@gentoo.org>
To: gentoo-python@lists.gentoo.org
Subject: Re: [gentoo-python] Timeframe for supporting Python versions
Date: Mon, 30 Apr 2012 23:01:52 +0200 [thread overview]
Message-ID: <4F9EFDC0.5030404@gentoo.org> (raw)
In-Reply-To: <CAKmKYaCTEi8ifpXA0XUgkObvC4YrKKqp_33QSO1EbLUM5wsk5A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]
On 30.04.2012 22:13, Dirkjan Ochtman wrote:
> On Mon, Apr 30, 2012 at 20:17, Kacper Kowalik <xarthisius@gentoo.org> wrote:
>> 1) how long are we supposed to keep old version of Python in Portage?
>> 2) how many version should we actively maintained?
>
> I'm not sure we need hard rules here. IMO the current approach (i.e.
> just talking about it and dropping as we decide it makes sense) is
> just fine. In particular, some version bumps are just harder than
> others, and adoption of new versions is always different (i.e. for 3.x
> and 2.x versions is obviously a very different story right now). From
> the other side (for example, in Mercurial depends), it also depends
> how big of a boon new features are.
>
> So let's just decide on a case-by-case when we deprecate a version? As
> for 2.5, are we seeing increased incompatibility yet? Any recent
> examples? I think 2.5 is close to deprecation, but I'm personally not
> getting the impression it's getting to be a big PITA just yet.
10% of packages that restrict Python abi in any way, restrict 2.5 (I've
grepped for "\(2.\[45\]\|2.5\)") That's the only statistics I could
think of.
I'm not aware of any security bugs related to 2.5 branch
Cheers,
Kacper
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]
next prev parent reply other threads:[~2012-04-30 21:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 18:17 [gentoo-python] Timeframe for supporting Python versions Kacper Kowalik
2012-04-30 20:13 ` Dirkjan Ochtman
2012-04-30 21:01 ` Kacper Kowalik [this message]
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=4F9EFDC0.5030404@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