From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SOwym-0007mQ-TO for garchives@archives.gentoo.org; Mon, 30 Apr 2012 20:13:53 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id BB71DE0BCD; Mon, 30 Apr 2012 20:13:49 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 84B32E0BCD for ; Mon, 30 Apr 2012 20:13:49 +0000 (UTC) Received: from mail-wg0-f53.google.com (mail-wg0-f53.google.com [74.125.82.53]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: djc) by smtp.gentoo.org (Postfix) with ESMTPSA id 9EEAC1B4091 for ; Mon, 30 Apr 2012 20:13:48 +0000 (UTC) Received: by wgbfm10 with SMTP id fm10so1076154wgb.10 for ; Mon, 30 Apr 2012 13:13:46 -0700 (PDT) Received: by 10.180.102.101 with SMTP id fn5mr9856644wib.6.1335816826125; Mon, 30 Apr 2012 13:13:46 -0700 (PDT) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Discussions centering around the Python ecosystem in Gentoo Linux X-BeenThere: gentoo-python@gentoo.org X-BeenThere: gentoo-python@lists.gentoo.org MIME-Version: 1.0 Received: by 10.216.137.162 with HTTP; Mon, 30 Apr 2012 13:13:25 -0700 (PDT) In-Reply-To: <4F9ED731.2000407@gentoo.org> References: <4F9ED731.2000407@gentoo.org> From: Dirkjan Ochtman Date: Mon, 30 Apr 2012 22:13:25 +0200 Message-ID: Subject: Re: [gentoo-python] Timeframe for supporting Python versions To: Kacper Kowalik Cc: gentoo-python@lists.gentoo.org Content-Type: text/plain; charset=UTF-8 X-Archives-Salt: 46e348b9-6b87-4189-bdbe-83f664f4706f X-Archives-Hash: 7139e99bfdabd9c8bdf45ea83ce992d9 On Mon, Apr 30, 2012 at 20:17, Kacper Kowalik 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. Cheers, Dirkjan