From mboxrd@z Thu Jan  1 00:00:00 1970
From: Christopher Allan Webber <cwebber@dustycloud.org>
Subject: Re: [PATCH] Update Python to 3.4.4
Date: Tue, 21 Jun 2016 09:44:25 -0500
Message-ID: <87oa6utxdi.fsf@dustycloud.org>
References: <87r3bru0rq.fsf@dustycloud.org> <20160620193509.GA8770@jasmine>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:42118)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cwebber@dustycloud.org>) id 1bFMus-0006wQ-Pl
	for guix-devel@gnu.org; Tue, 21 Jun 2016 10:44:39 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <cwebber@dustycloud.org>) id 1bFMuq-0005vC-V9
	for guix-devel@gnu.org; Tue, 21 Jun 2016 10:44:37 -0400
Received: from dustycloud.org ([2600:3c02::f03c:91ff:feae:cb51]:34158)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <cwebber@dustycloud.org>) id 1bFMuq-0005uE-RU
	for guix-devel@gnu.org; Tue, 21 Jun 2016 10:44:36 -0400
In-reply-to: <20160620193509.GA8770@jasmine>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel <guix-devel@gnu.org>

Leo Famulari writes:

> On Mon, Jun 20, 2016 at 02:18:49PM -0500, Christopher Allan Webber wrote:
>> Hello all!
>> 
>> Here's a patch to update Python to the latest version.  I can confirm
>> that it builds fine.  I'm guessing it needs to go into core-updates
>> though because this probably affects a lot of things?
>
> We received a patch for this a little while ago, and I think we wanted
> to work on 3.5 instead, since either 3.4.4 or 3.5 will require a lot of
> rebuilding. Maybe we should have a python-updates branch?

I have python-3.5 building here.  I'm working so that a python-3.4
package can still be kept around alongside that... verifying that it
builds successfully, then I'll submit a patch for Python 3.5 which
builds on this patch, so we can both update python3.4 to 3.4.4 and also
switch over most libraries programs to using python3.5 at the same time.

How does that sound?

 - Chris