From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxim Cournoyer Subject: Re: gnu: python-pytest: Update to 5.2.1. Date: Tue, 07 Jan 2020 17:39:35 -0500 Message-ID: <87muayvql4.fsf@gmail.com> References: <20191023072243.comuq7dmvnl67reo@rafflesia> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:60209) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ioxVm-0006jd-Gr for guix-devel@gnu.org; Tue, 07 Jan 2020 17:39:43 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ioxVl-0001jH-5W for guix-devel@gnu.org; Tue, 07 Jan 2020 17:39:42 -0500 Received: from mail-qk1-x744.google.com ([2607:f8b0:4864:20::744]:33664) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ioxVl-0001iv-22 for guix-devel@gnu.org; Tue, 07 Jan 2020 17:39:41 -0500 Received: by mail-qk1-x744.google.com with SMTP id d71so1005925qkc.0 for ; Tue, 07 Jan 2020 14:39:41 -0800 (PST) In-Reply-To: <20191023072243.comuq7dmvnl67reo@rafflesia> (Tanguy Le Carrour's message of "Wed, 23 Oct 2019 09:22:43 +0200") 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: Tanguy Le Carrour Cc: Guix Hello Tanguy, Tanguy Le Carrour writes: > Hi Guix! > > I'm working on updating python-pytest and=E2=80=A6 not everything is goin= g as > smoothly as I was expecting! :-( > > Pytest 5.2.1 depends on Pluggy >=3D0.12.0=E2=80=A6 which depends on > importlib-metadata. But when I had the latter as a propagated-input to > python-pluggy, then `guix build` gets stuck. > > diff --git a/gnu/packages/python-xyz.scm b/gnu/packages/python-xyz.scm > index a7f83dcd31..ab80cdebf9 100644 > --- a/gnu/packages/python-xyz.scm > +++ b/gnu/packages/python-xyz.scm > @@ -8914,17 +8914,19 @@ library as well as on the command line.") > (define-public python-pluggy > (package > (name "python-pluggy") > - (version "0.11.0") > + (version "0.13.0") > (source > (origin > (method url-fetch) > (uri (pypi-uri "pluggy" version)) > (sha256 > (base32 > - "10511a54dvafw1jrk75mrhml53c7b7w4yaw7241696lc2hfvr895")))) > + "0d4gsvb4kjqhiqqi4bbsdp7s1xlyl5phibcw1q1mrpd65xia2pzs")))) > (build-system python-build-system) > (native-inputs > `(("python-setuptools-scm" ,python-setuptools-scm))) > + (propagated-inputs > + `(("python-importlib-metadata" ,python-importlib-metadata))) > (synopsis "Plugin and hook calling mechanism for Python") > (description "Pluggy is an extraction of the plugin manager as us= ed by > Pytest but stripped of Pytest specific details.") > > The problem seems to be that python-importlib-metadata's dependency graph > contains=E2=80=A6 python-pluggy! > > How am I supposed to fix this chicken and egg situation?! Is this > something that should be notified to upstream?! > > Regards I think I had told you this over IRC, but for the record: Python 3.8 will include importlib-metadata in its core libraries, so after we move to it on core-updates the chicken and egg situation will be no more. Maxim