Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #8704 > unrolled thread
| Started by | Gordon Ball <gordon@chronitis.net> |
|---|---|
| First post | 2016-08-05 15:00 +0200 |
| Last post | 2016-08-05 22:40 +0200 |
| Articles | 5 — 3 participants |
Back to article view | Back to linux.debian.maint.python
Packaging/installing jupyter kernels Gordon Ball <gordon@chronitis.net> - 2016-08-05 15:00 +0200
Re: Packaging/installing jupyter kernels Julien Puydt <julien.puydt@laposte.net> - 2016-08-05 15:20 +0200
Re: Packaging/installing jupyter kernels Gordon Ball <gordon@chronitis.net> - 2016-08-05 21:00 +0200
Re: Packaging/installing jupyter kernels Julien Puydt <julien.puydt@laposte.net> - 2016-08-05 22:30 +0200
Re: Packaging/installing jupyter kernels Julien Cristau <jcristau@debian.org> - 2016-08-05 22:40 +0200
| From | Gordon Ball <gordon@chronitis.net> |
|---|---|
| Date | 2016-08-05 15:00 +0200 |
| Subject | Packaging/installing jupyter kernels |
| Message-ID | <s2MTf-7El-23@gated-at.bofh.it> |
Jupyter has been in experimental for a while and presumably will make it to unstable in the not too distant future. Once that is done, what is the correct way for packages providing a jupyter kernel to install it? * manually install kernel.json in /usr/share/jupyter/kernels/<pkgname>? * build-depend on python3-jupyter-core and call `jupyter kernelspec install` during build? * runtime-depend and install in postinst instead? * (something else) Gordon
[toc] | [next] | [standalone]
| From | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| Date | 2016-08-05 15:20 +0200 |
| Message-ID | <s2NcB-80H-9@gated-at.bofh.it> |
| In reply to | #8704 |
Hi, On 05/08/2016 14:07, Gordon Ball wrote: > Jupyter has been in experimental for a while and presumably will make it > to unstable in the not too distant future. I don't think that will happen that early... there are a few things not ready yet and what is there isn't perfect yet. Help is welcome! > Once that is done, what is the correct way for packages providing a > jupyter kernel to install it? > > * manually install kernel.json in /usr/share/jupyter/kernels/<pkgname>? > * build-depend on python3-jupyter-core and call `jupyter kernelspec > install` during build? > * runtime-depend and install in postinst instead? > * (something else) No idea. Snark on #debian-python
[toc] | [prev] | [next] | [standalone]
| From | Gordon Ball <gordon@chronitis.net> |
|---|---|
| Date | 2016-08-05 21:00 +0200 |
| Message-ID | <s2SvD-2Re-5@gated-at.bofh.it> |
| In reply to | #8705 |
On 05/08/16 15:17, Julien Puydt wrote: > Hi, > > On 05/08/2016 14:07, Gordon Ball wrote: >> Jupyter has been in experimental for a while and presumably will make it >> to unstable in the not too distant future. > > I don't think that will happen that early... there are a few things not > ready yet and what is there isn't perfect yet. Help is welcome! I might be able to help. What are the outstanding issues/blockers? (I'm not actually a DPMT/PAPT member, but this might be a good time to join). > >> Once that is done, what is the correct way for packages providing a >> jupyter kernel to install it? >> >> * manually install kernel.json in /usr/share/jupyter/kernels/<pkgname>? >> * build-depend on python3-jupyter-core and call `jupyter kernelspec >> install` during build? >> * runtime-depend and install in postinst instead? >> * (something else) > > No idea. Example: xonsh (a python-based shell) includes a kernel and tries to install it from setup.py (currently disabled by not having jupyter available at build time). But it sounds like the question is premature. > > Snark on #debian-python > chronitis on same
[toc] | [prev] | [next] | [standalone]
| From | Julien Puydt <julien.puydt@laposte.net> |
|---|---|
| Date | 2016-08-05 22:30 +0200 |
| Message-ID | <s2TUK-3Xw-11@gated-at.bofh.it> |
| In reply to | #8707 |
On 05/08/2016 20:57, Gordon Ball wrote: > On 05/08/16 15:17, Julien Puydt wrote: >> Hi, >> >> On 05/08/2016 14:07, Gordon Ball wrote: >>> Jupyter has been in experimental for a while and presumably will make it >>> to unstable in the not too distant future. >> >> I don't think that will happen that early... there are a few things not >> ready yet and what is there isn't perfect yet. Help is welcome! > > I might be able to help. What are the outstanding issues/blockers? > > (I'm not actually a DPMT/PAPT member, but this might be a good time to > join). I'm trying to finish nbconvert, with the notebook to come -- last time I had a look, we (Debian) were lacking javascript packages. So perhaps you need not join the DPMT after all :-P If you don't feel good with packaging javascript, you could also launch ipython (the one in experimental) and try to run a few commands in them. You should get a few warnings : those are hints something isn't quite right. >> >>> Once that is done, what is the correct way for packages providing a >>> jupyter kernel to install it? >>> >>> * manually install kernel.json in /usr/share/jupyter/kernels/<pkgname>? >>> * build-depend on python3-jupyter-core and call `jupyter kernelspec >>> install` during build? >>> * runtime-depend and install in postinst instead? >>> * (something else) >> >> No idea. > > Example: xonsh (a python-based shell) includes a kernel and tries to > install it from setup.py (currently disabled by not having jupyter > available at build time). But it sounds like the question is premature. > See above for ideas what to do -- but you can also try to find out what the better scheme to ship jupyter kernel is... I don't think anybody wondered seriously about it yet. :-) Cheers, Snark on #debian-python
[toc] | [prev] | [next] | [standalone]
| From | Julien Cristau <jcristau@debian.org> |
|---|---|
| Date | 2016-08-05 22:40 +0200 |
| Message-ID | <s2U4p-40L-3@gated-at.bofh.it> |
| In reply to | #8704 |
On Fri, Aug 5, 2016 at 14:07:51 +0200, Gordon Ball wrote: > Jupyter has been in experimental for a while and presumably will make it > to unstable in the not too distant future. > > Once that is done, what is the correct way for packages providing a > jupyter kernel to install it? > > * manually install kernel.json in /usr/share/jupyter/kernels/<pkgname>? > * build-depend on python3-jupyter-core and call `jupyter kernelspec > install` during build? > * runtime-depend and install in postinst instead? > * (something else) > The 'build-depend on jupyter-core and call kernelspec install during build' thing is what I've done for ipykernel, IIRC. Cheers, Julien
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.python
csiph-web