From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: [PATCH 0/2] Add new pytest for special cases
Date: Mon, 31 Oct 2016 10:19:07 +0100
Message-ID: <877f8okh9w.fsf@elephly.net>
References: <cover.1477867669.git.leo@famulari.name>
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]:50629)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1c18kZ-0006pO-FN
	for guix-devel@gnu.org; Mon, 31 Oct 2016 05:19:28 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rekado@elephly.net>) id 1c18kV-0000Og-LU
	for guix-devel@gnu.org; Mon, 31 Oct 2016 05:19:26 -0400
Received: from sender163-mail.zoho.com ([74.201.84.163]:21457)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <rekado@elephly.net>) id 1c18kV-0000Gp-DP
	for guix-devel@gnu.org; Mon, 31 Oct 2016 05:19:23 -0400
In-reply-to: <cover.1477867669.git.leo@famulari.name>
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@gnu.org


Leo Famulari <leo@famulari.name> writes:

> We package version 2.7.3 of pytest, which was released in September
> 2015. I guess that Python development moves very quickly, because there
> are already some packages whose test suites require a newer version of
> pytest.
>
> Notably, the most recent release of Borg, 1.0.8, requires something
> called 'tmpdir_factory', which was introduced in pytest 2.8 [0]. You can
> see this by building Borg on core-updates, where Python 3.5 makes the
> test suite run (it never ran on master with Python 3.4).
>
> 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.

~~ Ricardo