From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 0/2] Update Python to current versions Date: Mon, 25 Apr 2016 15:07:24 -0400 Message-ID: <20160425190724.GD17335@jasmine> References: <1461269926-7934-1-git-send-email-h.goebel@crazy-compilers.com> <57195E66.4010502@gmail.com> <5719C780.4050607@goebel-consult.de> <20160424001838.GB10040@jasmine> <87d1peadjm.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58806) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aulqy-0006B7-8l for guix-devel@gnu.org; Mon, 25 Apr 2016 15:07:29 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aulqu-0006Jm-7K for guix-devel@gnu.org; Mon, 25 Apr 2016 15:07:28 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:55969) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aulqu-0006JS-3n for guix-devel@gnu.org; Mon, 25 Apr 2016 15:07:24 -0400 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0E597298A9 for ; Mon, 25 Apr 2016 15:07:24 -0400 (EDT) Content-Disposition: inline In-Reply-To: <87d1peadjm.fsf@gnu.org> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ludovic =?iso-8859-1?Q?Court=E8s?= Cc: guix-devel@gnu.org, Hartmut Goebel On Sun, Apr 24, 2016 at 11:43:09PM +0200, Ludovic Courtès wrote: > Leo Famulari skribis: > > > On Fri, Apr 22, 2016 at 08:41:04AM +0200, Hartmut Goebel wrote: > >> Am 22.04.2016 um 01:12 schrieb Cyril Roelandt: > >> > I think the latest Python 3.x is Python 3.5.1 (see > >> > https://www.python.org/). Maybe we should forget about 3.4.x, WDYT? > >> > >> Python 3.4.4 is the latest version fon the 3.4 series. So we should > >> provide this too. (Esp. as long as 3.5 ist not packaged yet). > > > > As mentioned by others, updates to packages with many dependents are > > very computationally expensive, and so we try to do many of them in > > batches using the 'core-updates' branch of our Git repository. > > I’d suggest a ‘python-updates’ branch where we’d be able to pinpoint > breakage due specifically to these updates. In that case, we should also try to update python-setuptools, and possibly some other "core" Python packages. I've noticed some upstream "minimum version of setuptools" requirements creepings towards our version.