From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: [PATCH 0/2] Add new pytest for special cases Date: Mon, 31 Oct 2016 13:20:02 -0400 Message-ID: <20161031172002.GA31367@jasmine> References: <877f8okh9w.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:60741) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c1GFl-0001cM-P7 for guix-devel@gnu.org; Mon, 31 Oct 2016 13:20:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c1GFg-00075b-Rp for guix-devel@gnu.org; Mon, 31 Oct 2016 13:20:09 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:59856) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1c1GFg-00075J-M0 for guix-devel@gnu.org; Mon, 31 Oct 2016 13:20:04 -0400 Content-Disposition: inline In-Reply-To: <877f8okh9w.fsf@elephly.net> 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: Ricardo Wurmus Cc: guix-devel@gnu.org On Mon, Oct 31, 2016 at 10:19:07AM +0100, Ricardo Wurmus wrote: > Leo Famulari writes: > > I'd really prefer to run the Borg tests, so I want to add a newer > > release of pytest and use it with Borg. > > > > I've been testing pytest upgrades locally, and there is some breakage, > > so I think we should not try to upgrade it for all packages in this > > core-updates cycle. Instead, I want to build on Hartmut's > > wip-python-build-system to upgrade the core Python packages after this > > core-updates cycle. > > > > WDYT? > > This makes sense. I looked over the patches and they look good to me. > > We have a lot of Python packages that really should be updated. We need > some Python champions to take care of continued updates there. Please check out Hartmut's wip-python-build-system branch :) I read through the commits a couple days ago, and the general idea seems reasonable, although I don't understand everything yet. If we decide to continue with that approach, I will help upgrade the core Python packages on top of it. If not, I'll recreate the old wip-python branch after this core-updates cycle is merged; I wanted to wait for Python 3.5 before continuing.