all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Konrad Hinsen <konrad.hinsen@fastmail.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Towards reproducibly Jupyter notebooks with Guix-Jupyter
Date: Mon, 14 Oct 2019 13:45:57 +0200	[thread overview]
Message-ID: <m1lftnpn2i.fsf@ordinateur-de-catherine--konrad.home> (raw)
In-Reply-To: <875zkru70u.fsf@inria.fr>

Hi Ludo,

> (Though printing addresses in a REPL isn’t “bad practice” IMO, it’s just
> that it doesn’t mesh well with the intended use of notebooks.)

And that's exactly the difference between a REPL and a reproducible
document. Unfortunately, Jupyter tries to be both and thus never
explains the differences clearly.

> At the API level, there’s ‘inferior-for-channels’ which does that +
> registers a GC root + maintains a cache so that the second time you use
> a given instance of Guix it’s immediately available.

Just what I need...

> Now, I think you can safely use it in your code, I don’t foresee any
> significant change at this point.
>
> As to whether you’d want to talk about it in the MOOC for instance, you

Certainly not. I just want to be sure that the functionality won't go
away. If the API changes a bit, that can be fixed.

I'll start playing with this...

Cheers,
  Konrad.

  reply	other threads:[~2019-10-14 11:46 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1lftnpn2i.fsf@ordinateur-de-catherine--konrad.home \
    --to=konrad.hinsen@fastmail.net \
    --cc=guix-devel@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.