Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #7286
| From | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Packaging the Jupyter project suite |
| Date | 2015-09-18 18:00 +0200 |
| Message-ID | <qa6eT-75X-43@gated-at.bofh.it> (permalink) |
| Organization | linux.* mail to news gateway |
Hi, I would like to package the Jupyter suite of software (ex-IPython). Of course, that makes quite a few packages to prepare, with a big dependency graph. I already sent a few ITP (pickleshare, traitlets), a few RFS (path.py), some are in NEW (ipython-genutils)... What is annoying is that some of the packages have a dependency chain going in some way, and an extra dependency chain going the other way. For a concrete example, ipykernel depends on ipython... but ipython has an extra-dep on ipykernel. How does one package something like this? Does someone want to lend a hand? Thanks, Snark on #debian-python
Back to linux.debian.maint.python | Previous | Next — Next in thread | Find similar
Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-18 18:00 +0200
Re: Packaging the Jupyter project suite Thomas Kluyver <takluyver@fastmail.com> - 2015-09-19 00:10 +0200
Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-19 07:20 +0200
Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-21 21:00 +0200
Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-21 21:10 +0200
Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-25 07:50 +0200
Re: Packaging the Jupyter project suite Julien Puydt <julien.puydt@laposte.net> - 2015-09-25 14:30 +0200
Re: Packaging the Jupyter project suite Julien Cristau <julien.cristau@logilab.fr> - 2015-09-25 14:30 +0200
csiph-web