> +(define-public python-plyer > + (package > + (name "python-plyer") > + [...] > + (arguments > + `(#:tests? #f)) ;; Circular dependency on itself Seems odd that python-plyer's tests cannot find python-plyer, but whatever. You can try to work-around the cycle by defining two python-plyer packages, like this (fill in the ...): (define-public python-plyer (package (name ...) (version ...) (build-system ...) ;; do not add (arguments ...) here! ;; (This comment should not go into the revised patch) (native-inputs ;; Add a comment on why this is necessary `(("python-plyer" ,python-plyer-for-tests))) (home-page ...) (synopsis ...) (description ...))) (define python-plyer-for-tests (package/hidden (inherit python-plyer) (native-inputs '()))) That way, first a python-plyer without tests will be built, and then the real python-plyer will be built with tests. Greetings, Maxime.