Roel Janssen <r...@gnu.org> writes: > Ricardo Wurmus writes: > >> * gnu/packages/python.scm (python-jupyter-client, >> python2-jupyter-client): New variables. >> --- >> gnu/packages/python.scm | 32 ++++++++++++++++++++++++++++++++ >> 1 file changed, 32 insertions(+) >> >> diff --git a/gnu/packages/python.scm b/gnu/packages/python.scm >> index da16647..09ce599 100644 >> --- a/gnu/packages/python.scm >> +++ b/gnu/packages/python.scm >> @@ -4525,6 +4525,38 @@ without using the configuration machinery.") >> (define-public python2-jupyter-core >> (package-with-python2 python-jupyter-core)) >> >> +(define-public python-jupyter-client >> + (package >> + (name "python-jupyter-client") >> + (version "4.4.0") >> + (source >> + (origin >> + (method url-fetch) >> + (uri (pypi-uri "jupyter_client" version)) >> + (sha256 >> + (base32 >> + "1vjjrpjw7k5sh982pbjnslv7byfbfazjw9g92jvs7dz5qbx556n9")))) >> + (build-system python-build-system) >> + ;; Tests fail because of missing native python kernel which I assume is >> + ;; provided by the ipython package, which we cannot use because it would >> + ;; cause a dependency cycle. >> + (arguments `(#:tests? #f)) >> + (propagated-inputs >> + `(("python-pyzmq" ,python-pyzmq) >> + ("python-traitlets" ,python-traitlets) >> + ("python-jupyter-core" ,python-jupyter-core))) >> + (home-page "http://jupyter.org/") >> + (synopsis "Jupyter protocol implementation and client libraries") >> + (description >> + "The @code{jupyter_client} package contains the reference >> implementation >> +of the Jupyter protocol. It also provides client and kernel management APIs >> +for working with kernels, and the @code{jupyter kernelspec} entrypoint for >> +installing kernelspecs for use with Jupyter frontends.") >> + (license license:bsd-3))) > > Is "kernelspec" one word? And should "kernelspecs" be "@code{kernelspec}s"?
It probably should be wrapped in @code{}. Will do this before pushing. ~~ Ricardo