Roel Janssen <r...@gnu.org> writes: > Ricardo Wurmus writes: > >> * gnu/packages/python.scm (python-jupyter-core, python2-jupyter-core): >> New variables. >> --- >> gnu/packages/python.scm | 25 +++++++++++++++++++++++++ >> 1 file changed, 25 insertions(+) >> >> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm >> index c612846..da16647 100644 >> --- a/gnu/packages/python.scm >> +++ b/gnu/packages/python.scm >> @@ -4500,6 +4500,31 @@ without using the configuration machinery.") >> (define-public python2-traitlets >> (package-with-python2 python-traitlets)) >> >> +(define-public python-jupyter-core >> + (package >> + (name "python-jupyter-core") >> + (version "4.2.0") >> + (source >> + (origin >> + (method url-fetch) >> + (uri (string-append (pypi-uri "jupyter_core" version))) >> + (sha256 >> + (base32 >> + "177d9csqldzhsh6xs1p4nf6lzvhzyg6gklqjf69lxgxyadx87v24")))) >> + (build-system python-build-system) >> + ;; FIXME: not sure how to run the tests >> + (arguments `(#:tests? #f)) > > Any idea?
This might be fixed by upgrading pytest, but I haven’t played with this yet. Will do so once we have the new pytest. Another common problem with these Jupyter packages is that many of the tests are integration tests, so they depend on many other Jupyter packages, causing dependency loops. It’s not pretty. ~~ Ricardo
