Return-Path: X-Original-To: apmail-aurora-dev-archive@minotaur.apache.org Delivered-To: apmail-aurora-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BEA8611C76 for ; Thu, 17 Jul 2014 19:33:17 +0000 (UTC) Received: (qmail 28583 invoked by uid 500); 17 Jul 2014 19:33:17 -0000 Delivered-To: apmail-aurora-dev-archive@aurora.apache.org Received: (qmail 28536 invoked by uid 500); 17 Jul 2014 19:33:17 -0000 Mailing-List: contact dev-help@aurora.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aurora.incubator.apache.org Delivered-To: mailing list dev@aurora.incubator.apache.org Received: (qmail 28525 invoked by uid 99); 17 Jul 2014 19:33:17 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 19:33:17 +0000 X-ASF-Spam-Status: No, hits=-1997.8 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.3] (HELO mail.apache.org) (140.211.11.3) by apache.org (qpsmtpd/0.29) with SMTP; Thu, 17 Jul 2014 19:33:15 +0000 Received: (qmail 23327 invoked by uid 99); 17 Jul 2014 19:32:55 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 19:32:55 +0000 Received: from localhost (HELO mail-vc0-f170.google.com) (127.0.0.1) (smtp-auth username wfarner, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Thu, 17 Jul 2014 19:32:55 +0000 Received: by mail-vc0-f170.google.com with SMTP id lf12so5464723vcb.29 for ; Thu, 17 Jul 2014 12:32:54 -0700 (PDT) X-Gm-Message-State: ALoCoQkhbjbHnaxF8VNL8I2/IQEwNaztY3p9UrDnXOjAAeX91ywlR2VWP80FuiGl+Bi/U179PiM0 MIME-Version: 1.0 X-Received: by 10.220.187.134 with SMTP id cw6mr42425482vcb.3.1405625574376; Thu, 17 Jul 2014 12:32:54 -0700 (PDT) Received: by 10.58.34.198 with HTTP; Thu, 17 Jul 2014 12:32:54 -0700 (PDT) In-Reply-To: References: Date: Thu, 17 Jul 2014 12:32:54 -0700 Message-ID: Subject: Re: Python versions (redux) From: Bill Farner To: "dev@aurora.incubator.apache.org" Content-Type: multipart/alternative; boundary=089e01537c1e0c61a104fe68b5c5 X-Virus-Checked: Checked by ClamAV on apache.org --089e01537c1e0c61a104fe68b5c5 Content-Type: text/plain; charset=UTF-8 Bhuvan's link [2] was the clincher for me. +1 to dropping support, as the python developers have. -=Bill On Thu, Jul 17, 2014 at 12:11 PM, Bhuvan Arumugam wrote: > Only reason I could think of supporting py26 is to support rhel6.x > customers. Now that rhel7 is out [1], it make sense to discontinue > support for py26. We should document it in supported platforms though. > We should add a pointer for rhel6.x customers to upgrade python. > > It also make sense as py26 is already eol [2]. > > That said, +1 to discontinue support for py26. > > [1] > http://www.redhat.com/about/news/press-archive/2014/6/red-hat-unveils-rhel-7 > [2] > https://mail.python.org/pipermail/python-dev/2013-September/128287.html > > > On Thu, Jul 17, 2014 at 11:46 AM, Mark Chu-Carroll > wrote: > > A couple of months ago, we had a discussion about which python versions > to > > support. (See > > > http://mail-archives.apache.org/mod_mbox/incubator-aurora-dev/201404.mbox/%3CCAFGkSCk71%2BziUQCsnMfStr-ucrT52DLEgBfHA-o097683PstLQ%40mail.gmail.com%3E > > to refresh your memory.) > > > > At the time, we punted on it, because we had a convenient workaround. But > > python version issues have continued to pop up from time to time. In > > particular, we've had issues like the current > > https://issues.apache.org/jira/browse/AURORA-585. > > > > The question that I'd like to put forward is: how much effort is it work > to > > continue to support Python 2.6? The Python maintainers are no longer > > maintaining 2.6 - the download page for the last release of 2.6 says: > > "With the 2.6.9 release, and five years after its first release, the > > Python 2.6 series is now officially retired. All official maintenance for > > Python 2.6, including security patches, has ended. For ongoing > maintenance > > releases, please see the Python 2.7 series. The NEWS file lists every > > change in each alpha, beta, release candidate, and final release of > Python > > 2.6." > > > > We certainly *can* continue to support Python2.6, but it's likely to be a > > non-trivial effort. Is it worth it? > > > > (Full disclosure, in case it's not obvious: I think as a provider of a > > distributed computing platform, continuing to support a python > interpreter > > that won't even get security fixes is not a good idea. I'm in favor of > > dropping 2.6.) > > > > -Mark > > > > -- > Regards, > Bhuvan Arumugam > www.livecipher.com > --089e01537c1e0c61a104fe68b5c5--