From: OLIVER HENRIOT <oliver.henriot@univ-grenoble-alpes.fr>
To: help-guix@gnu.org
Subject: python package dependencies conflict, pydot, ipython and pyparsings
Date: Mon, 17 Jul 2023 15:28:40 +0200 (CEST) [thread overview]
Message-ID: <1693762243.2587011.1689600520057.JavaMail.zimbra@univ-grenoble-alpes.fr> (raw)
Hi Guix!
I'm trying to use both python-pydot and python-ipython and I'm stumbling accross a dependency problem. Pydot specifies pyparsings 2.4.7 as a propagated input. Ipython requires version 3.0.6.
guix package: error: profile contains conflicting entries for python-pyparsing
guix package: error: first entry: python-pyparsing@2.4.7 /gnu/store/m7gzn7yw5g6f3ba3mrkc55pifl757hrb-python-pyparsing-2.4.7
guix package: error: ... propagated from python-pydot@1.4.2
guix package: error: second entry: python-pyparsing@3.0.6 /gnu/store/wlmf5spfdmsjiw6cx30h0rpydfpz3gil-python-pyparsing-3.0.6
guix package: error: ... propagated from python-packaging@21.3
guix package: error: ... propagated from python-sphinx@5.1.1
guix package: error: ... propagated from python-numpydoc@1.5.0
guix package: error: ... propagated from python-ipython@8.5.0
I thought naively that both versions could coexist (they are both present in the store) but there is visibly some magic missing to make this work within my manifest.
I did a dirty hack, copied the content of pydot from graphviz.scm to a personal channel repository package, edited to remove the reference to the pyparsing version and it installs nicely alongside ipython and all the other the packages in my manifest (I did have to disable the tests, `delete 'check)` instead of the existing `replace 'check) sequence as it genrated errors but it should have no impact on dependencies I presume and re-introducing checks "just" requires debugging). Relevant excerpt from my dirty hack package definition:
(define-public my-python-pydot
(package
(name "my-python-pydot")
(version "1.4.2")
(source
(origin
(method url-fetch)
(uri (pypi-uri "pydot" version))
(sha256
(base32
"0z80zwldf7ffkwrpm28hixsiqp3053j7g281xd6phmnbkfiq3014"))))
(build-system python-build-system)
(arguments
'(#:phases
(modify-phases %standard-phases
;; checks disabled for testing
(delete 'sanity-check)
(delete 'check))))
(propagated-inputs
(list python-pyparsing))
(home-page "https://github.com/pydot/pydot")
(synopsis "Python interface to Graphviz's DOT language")
(description
"Pydot provides an interface to create, handle, modify and process
graphs in Graphviz's DOT language, written in pure Python.")
(license license:expat)))
Pydot can then be imported in the python interpreter and a simple graph as given on the project's pypi page ( [ https://pypi.org/project/pydot/ | https://pypi.org/project/pydot/ ] ) works so I presume this is functionnal (haven't run further tests, I don't know pydot syntax well enough). Is there a reason I have missed to specify this precise version of pyparsings as a dependency for pydot in the official repo? If so, can I nonetheless have both ipython and pydot at the same time in my manifest using some magic trick?
Thanks!
Oliver
Oliver Henriot OSUG - ISTerre
ISDeform / RENAg
1381 rue de la piscine
33 (0)4 57 42 18 62
[ https://www.isterre.fr/ | isterre.fr ] [ http://www.univ-grenoble-alpes.fr/ ]
next reply other threads:[~2023-07-17 18:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 13:28 OLIVER HENRIOT [this message]
2023-08-18 17:16 ` python package dependencies conflict, pydot, ipython and pyparsings Simon Tournier
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=1693762243.2587011.1689600520057.JavaMail.zimbra@univ-grenoble-alpes.fr \
--to=oliver.henriot@univ-grenoble-alpes.fr \
--cc=help-guix@gnu.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.
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).