[bug#57056,v3,2/3] gnu: python-pluggy: Update to 1.0.0.
 
Commit Message
  
  
* gnu/packages/python-xyz.scm (python-pluggy): Update to 1.0.0.
  [propagated-inputs]: Add python-importlib-metadata.
---
 gnu/packages/python-xyz.scm | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)
  
 
Comments
  
  
> * gnu/packages/python-xyz.scm (python-pluggy): Update to 1.0.0.
>   [propagated-inputs]: Add python-importlib-metadata.
Turns out this one was causing an infinite evaluation loop and I had to
revert it just before pushing.
Could it be because of the python-importlib-metadata inclusion?
Thanks,
Mathieu
  
 
  
  
> Could it be because of the python-importlib-metadata inclusion?
I would rather bet on the presence of pluggy in pytest inputs, and the
presence of pytest in the build system, or something like that.
I can't look at that today, but I will investigate that.
  
 
  
@@ -14511,17 +14511,17 @@  (define-public python-rsa
 (define-public python-pluggy
   (package
    (name "python-pluggy")
-   (version "0.13.1")
+   (version "1.0.0")
    (source
     (origin
      (method url-fetch)
      (uri (pypi-uri "pluggy" version))
      (sha256
       (base32
-       "1c35qyhvy27q9ih9n899f3h4sdnpgq027dbiilly2qb5cvgarchm"))))
+       "0n8iadlas2z1b4h0fc73b043c7iwfvx9rgvqm1azjmffmhxkf922"))))
    (build-system python-build-system)
-   (native-inputs
-    (list python-setuptools-scm))
+   (propagated-inputs (list python-importlib-metadata))
+   (native-inputs (list python-setuptools-scm))
    (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.")