From mboxrd@z Thu Jan  1 00:00:00 1970
From: Giovanni Biscuolo <g@xelera.eu>
Subject: Re: gnu: python-pytest: Update to 5.2.1.
Date: Wed, 23 Oct 2019 17:47:17 +0200
Message-ID: <87zhhrtqey.fsf@roquette.mug.biscuolo.net>
References: <20191023072243.comuq7dmvnl67reo@rafflesia>
 <20191023080047.GD20347@E5400>
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:470:142:3::10]:42839)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <g@xelera.eu>) id 1iNIrB-0006EX-Cr
 for guix-devel@gnu.org; Wed, 23 Oct 2019 11:47:30 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <g@xelera.eu>) id 1iNIrA-0008LT-4u
 for guix-devel@gnu.org; Wed, 23 Oct 2019 11:47:29 -0400
Received: from ns13.heimat.it ([46.4.214.66]:39314)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <g@xelera.eu>)
 id 1iNIr9-0008Ie-Uf
 for guix-devel@gnu.org; Wed, 23 Oct 2019 11:47:28 -0400
In-Reply-To: <20191023080047.GD20347@E5400>
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: <https://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: Efraim Flashner <efraim@flashner.co.il>, Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix <guix-devel@gnu.org>

Hi Efraim,

Efraim Flashner <efraim@flashner.co.il> writes:

[...]

> I assume python-importlib-metadata only needs python-pytest for running
> the test suite. We have a couple of python libraries that have
> '-bootstrap' added to the end. You could try making a
> python-importlib-metadata-bootstrap which doesn't use python-pytest and
> doesn't run the test suite, and use that as an input for python-pytest.
>
> Or if that's not the circle that's created then you'll have to find
> where it is. Same advice though, create another package with less
> functionality or without tests and use that to break the cycle.

This is an interesting advice, AFAIU it deserves a specific section in
the Cookbook but I'm not able to elaborate and clearly document how to
"break the cycle": please Efraim are you willing to elaborate and send a
patch for this?

[...]

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures