From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: Guix <guix-devel@gnu.org>
Subject: Re: gnu: python-pytest: Update to 5.2.1.
Date: Thu, 24 Oct 2019 20:42:32 -0400 [thread overview]
Message-ID: <87imodejuv.fsf@gmail.com> (raw)
In-Reply-To: <87r233we00.fsf@devup.no> (Marius Bakke's message of "Wed, 23 Oct 2019 19:47:11 +0200")
Hello,
Marius Bakke <mbakke@fastmail.com> writes:
> 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?!
>
> It would be great if you can make upstream aware of the issue.
>
> Note that if you just want to be able to use Pytest 5.x on the master
> branch, you can instead add a separate 'python-pluggy-0.13' variable and
> use that for 'python-pytest-5'.
>
> We'll still need to break the cycle in 'core-updates' though...
I too had looked into updating python-pytest, and realized the same
thing. There's a way out, though. Python 3.8.0 will include
'import-metadata' as a core library [0].
Let's package Python 3.8.0 on core-updates!
[0] https://docs.python.org/3/whatsnew/3.8.html#new-modules
Maxim
next prev parent reply other threads:[~2019-10-25 0:42 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 [this message]
2019-10-25 6:49 ` Tanguy Le Carrour
2020-01-07 22:39 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87imodejuv.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).