From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter
Date: Thu, 27 Feb 2020 20:48:32 +0100 [thread overview]
Message-ID: <CAJ3okZ2ecsKSVX1RQOczuQ=r=qTHsVtZGCHD-1c0Um6-z1cZRw@mail.gmail.com> (raw)
In-Reply-To: <87ftevizw3.fsf@elephly.net>
On Thu, 27 Feb 2020 at 20:39, Ricardo Wurmus <rekado@elephly.net> wrote:
> zimoun <zimon.toutoune@gmail.com> writes:
> > On Thu, 27 Feb 2020 at 19:43, Vincent Legoll <vincent.legoll@gmail.com> wrote:
> >> On Thu, Feb 27, 2020 at 7:20 PM zimoun <zimon.toutoune@gmail.com> wrote:
> >> > Because other kernels are named: python-ipykernel or ruby-iruby.
> >> > Another: python-pari-jupyter.
> >> > And another other: jupyter-guile-kernel.
> >> > Well, there is no real convention yet, if I understand correctly.
> >> >
> >> > A good move should to start a gnu/packages/jupyter.scm to put all the
> >> > Jupyter related machinery inside... I do not know.
> >>
> >> Maybe we can help them show up properly in guix search results, like
> >> adding what could be missing in description.
> >
> > Hum? I am not convinced that something is missing in the
> > description... I mean "guix search jupyter kernel | less" does already
> > the job, IMHO.
> > What should be missing is some convention in the naming scheme; and it
> > seems easier to force a convention when all the same related packages
> > live in the same file.
>
> The name r-irkernel follows the R package convention; a similar reason
> applies to python-ipykernel and ruby-iruby.
Yes, I know. :-)
Well, "it seems easier to force a convention when all the same related
packages live in the same file" so the current convention is the
cran.scm, ruby.scm or python.scm one. And I was suggesting to move the
packages related to Jupyter to its own module using the convention
'jupyter-' convention, e.g., 'jupyter-irkernel'. And even a more
uniformized naming scheme between all the kernels. As I said, I do not
know if it is a good idea or not. :-)
Cheers,
simon
next prev parent reply other threads:[~2020-02-27 19:48 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-10 8:21 Towards reproducibly Jupyter notebooks with Guix-Jupyter Ludovic Courtès
2019-10-10 8:59 ` zimoun
2019-10-10 10:07 ` Ludovic Courtès
2019-10-10 11:02 ` Konrad Hinsen
2019-10-10 14:52 ` Ludovic Courtès
2019-10-14 6:35 ` Konrad Hinsen
2019-10-14 7:21 ` Ludovic Courtès
2019-10-14 11:45 ` Konrad Hinsen
2019-10-14 13:25 ` Ludovic Courtès
2019-10-21 12:50 ` Konrad Hinsen
2019-10-22 10:16 ` Ludovic Courtès
2019-10-22 11:12 ` Konrad Hinsen
2019-10-24 10:26 ` Ludovic Courtès
2019-10-25 9:21 ` Konrad Hinsen
2019-10-29 14:16 ` Konrad Hinsen
2019-10-29 15:00 ` Pierre Neidhardt
2020-02-27 14:25 ` Pjotr Prins
2020-02-27 14:36 ` zimoun
2020-02-27 18:11 ` Pjotr Prins
2020-02-27 18:20 ` zimoun
2020-02-27 18:43 ` Vincent Legoll
2020-02-27 18:49 ` zimoun
2020-02-27 19:38 ` Ricardo Wurmus
2020-02-27 19:48 ` zimoun [this message]
2019-10-23 9:53 ` Konrad Hinsen
2019-10-23 10:32 ` zimoun
2019-10-23 12:15 ` Konrad Hinsen
2019-10-23 16:49 ` zimoun
2019-10-24 6:20 ` Konrad Hinsen
2019-10-24 13:23 ` Pierre Neidhardt
2019-10-25 14:29 ` Konrad Hinsen
2019-10-25 14:40 ` Pierre Neidhardt
2019-10-10 10:19 ` Roel Janssen
2019-10-10 11:59 ` Ludovic Courtès
2019-10-10 14:57 ` Ludovic Courtès
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='CAJ3okZ2ecsKSVX1RQOczuQ=r=qTHsVtZGCHD-1c0Um6-z1cZRw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).