From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Tanguy Le Carrour <tanguy@bioneland.org>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: gnu: python-pytest: Update to 5.2.1.
Date: Tue, 07 Jan 2020 17:39:35 -0500 [thread overview]
Message-ID: <87muayvql4.fsf@gmail.com> (raw)
In-Reply-To: <20191023072243.comuq7dmvnl67reo@rafflesia> (Tanguy Le Carrour's message of "Wed, 23 Oct 2019 09:22:43 +0200")
Hello Tanguy,
Tanguy Le Carrour <tanguy@bioneland.org> writes:
> Hi Guix!
>
> I'm working on updating python-pytest and… not everything is going as
> smoothly as I was expecting! :-(
>
> Pytest 5.2.1 depends on Pluggy >=0.12.0… 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 used by
> Pytest but stripped of Pytest specific details.")
>
> The problem seems to be that python-importlib-metadata's dependency graph
> contains… 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
next prev parent reply other threads:[~2020-01-07 22:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-23 7:22 gnu: python-pytest: Update to 5.2.1 Tanguy Le Carrour
2019-10-23 8:00 ` Efraim Flashner
2019-10-23 15:47 ` Giovanni Biscuolo
2019-10-23 17:47 ` Marius Bakke
2019-10-25 0:42 ` Maxim Cournoyer
2019-10-25 6:49 ` Tanguy Le Carrour
2020-01-07 22:39 ` Maxim Cournoyer [this message]
2020-01-08 7:48 ` Tanguy Le Carrour
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muayvql4.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=tanguy@bioneland.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.