unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Fis Trivial <ybbs.daans@hotmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "30921@debbugs.gnu.org" <30921@debbugs.gnu.org>
Subject: bug#30921: Jupyter uses the wrong Python.
Date: Sat, 24 Mar 2018 14:57:29 +0000	[thread overview]
Message-ID: <MWHPR16MB0063C6ED0A8672EE33A1BE0292AF0@MWHPR16MB0063.namprd16.prod.outlook.com> (raw)
In-Reply-To: <87tvt5ixmc.fsf@elephly.net>


Ricardo Wurmus writes:

> Fis Trivial <ybbs.daans@hotmail.com> writes:
>
>> When running jupyter, it seems that the python in "/usr/bin/python"
>> instead of the one in store is used. Here is the complete logging of
>> jupyter console output, notice those line in the middle, where displaying:
>> "/usr/bin/python: No module named ipykernel_launcher"
>
> I wonder if that’s by design.  As far as I understand Jupyter can be
> used with many different kernels, including different versions of
> Python.  This means that we may not limit it to just a single version of
> Python at build time.
>
> Is this correct?
>

Actually the only command I know about jupyter is how to open a
notebook :) . But it asks me to restart the kernel again and again in
browser. And according to the console, it seems that jupyter couldn't
find the needed kernel because the kernel is installed in guix store,
not in normal system path, but jupyter itself is ran by system
python other than the one installed in guix store.

And, maybe I am wrong, packages that installed by guix should never use
software not in the store, right?


> I do agree, though, that the default doesn’t seem right.  As long as a
> user can override the kernel to use a different Python than the one we
> configured at build time, I think we should default to the current
> version of Python in Guix.


  reply	other threads:[~2018-03-24 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24  6:55 bug#30921: Jupyter uses the wrong Python Fis Trivial
2018-03-24 10:19 ` Ricardo Wurmus
2018-03-24 14:57   ` Fis Trivial [this message]
2018-03-25  9:39   ` Konrad Hinsen
2018-07-02 13:06     ` Ludovic Courtès
2018-07-02 13:37       ` Konrad Hinsen
2018-07-02 15:10         ` 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=MWHPR16MB0063C6ED0A8672EE33A1BE0292AF0@MWHPR16MB0063.namprd16.prod.outlook.com \
    --to=ybbs.daans@hotmail.com \
    --cc=30921@debbugs.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).