unofficial mirror of guix-science@gnu.org 
 help / color / mirror / Atom feed
From: "Ludovic Courtès" <ludovic.courtes@inria.fr>
To: info-guix@gnu.org, guix-science@gnu.org
Subject: Guix-Jupyter 0.2.1 released
Date: Mon, 25 Jan 2021 16:15:34 +0100	[thread overview]
Message-ID: <87zh0x59pl.fsf@gnu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 3001 bytes --]

I’m pleased to announce the release of Guix-Jupyter 0.2.1!
Read more about this announcement at:

  https://hpc.guix.info/blog/2021/01/guix-jupyter-0.2.1-released/

• Download

  You can obtain it from Guix by running ‘guix pull’ followed by:

    guix environment --ad-hoc jupyter guix-jupyter -- jupyter notebook

  Alternatively, you can get the source from Git:

    git clone https://gitlab.inria.fr/guix-hpc/guix-kernel guix-jupyter
    cd guix-jupyter
    git checkout v0.2.1  # or a887e449cbf248113b25eac05507bd949c826554
    git tag -v v0.2.1

  The ‘git tag -v’ command checks the authenticity of your checkout.
  You may need to retrieve the signing key first:

    gpg --keyserver pool.sks-keyservers.net \
        --recv-keys 3CE464558A84FDC69DB40CFB090B11993D9AEBB5

• About

  Guix-Jupyter is a Jupyter “kernel” that interprets software deployment
  annotations, thereby making sure computations run in the right
  software environment.  Cells execute in isolated containers, which
  furthers reduces the risks of non-reproducibility.  Input data can be
  fetched by using an extra annotation, which must include the expected
  hash of the data.

• Excerpt from the ‘NEWS’ file

  * Changes in 0.2.1 (since 0.2.0)

  ** Bug fix

     Previously Guix-Jupyter would store container data in
     /tmp/guix-kernel, which prevented multiple users from running it on
     the same machine.  It now uses mkdtemp(3) to create that directory.

  * Changes in 0.2.0 (since 0.1.0)

  ** New functionality

  *** New ‘;;guix describe’ magic command

      Like the ‘guix describe’ shell command, it returns the currently-used
      channels.

  *** New ‘;;guix search’ magic command

      Return the list of packages matching the given patterns.

  *** ‘;;guix pin’ and ‘;;guix describe’ output includes links to VCS history

      This allows you to see the version-control system (VCS) history
      leading to the channel commit you’re using.

  *** Report build and download progress in the notebook

      When Guix starts downloading or building things, for instance in
      response to an environment creation via ‘;;guix environment’, a
      transient line in the notebook displays what’s being built or
      downloaded.

  *** Guile kernel can display SVG pictures

      The built-in Guile kernel now returns SVG for images produced by
      ‘guile-picture-language’ (see
      https://git.elephly.net/software/guile-picture-language.git).

  ** Bug fixes

  *** Gracefully handle package-not-found errors in ‘;;guix environment’

  *** Properly complete ‘;;guix’ magic commands

  *** Fix potential hang in ‘;;guix pin’

  *** Gracefully handle ‘;;guix download’ syntax errors


You can report bugs and send patches to <guix-science@gnu.org> or on the
web site:

  https://gitlab.inria.fr/guix-hpc/guix-kernel

Ludo’.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 869 bytes --]

                 reply	other threads:[~2021-01-25 15:20 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=87zh0x59pl.fsf@gnu.org \
    --to=ludovic.courtes@inria.fr \
    --cc=guix-science@gnu.org \
    --cc=info-guix@gnu.org \
    /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.
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).