unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Dan.Munteanu@mdc-berlin.de" <Dan.Munteanu@mdc-berlin.de>
To: 57648@debbugs.gnu.org
Subject: bug#57648: python-bash-kernel : No module named bash_kernel
Date: Tue, 6 Sep 2022 23:08:01 +0000	[thread overview]
Message-ID: <00f155bff5d649a49a129e47a4e2851f490887b3.camel@mdc-berlin.de> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1166 bytes --]

Hi,

I've tried to use python-bash-kernel (via jupyterhub), but, even the
package installation defines  correctly the kernel

$ cat .guix-profile/share/jupyter/kernels/bash/kernel.json 
{"argv": ["/gnu/store/1m48ama708vh9cjn79yw6cj8sgg7pa1b-python-wrapper-
3.9.9/bin/python", "-m", "bash_kernel", "-f", "{connection_file}"],
"codemirror_mode": "shell", "display_name": "Bash", "env": {"PS1":
"$"}, "language": "bash"}

it fails  with the "No module found" error:

/gnu/store/1m48ama708vh9cjn79yw6cj8sgg7pa1b-python-wrapper-
3.9.9/bin/python: No module named bash_kernel

I've managed to use the kernel with one of the following workarounds:

 - define an env variable GUIX_PYTHONPATH (.bashrc or .bashprofile) set
to .guix-profile/lib/python3.9/site-packages/
 - added a new line in share/jupyter/bash/kernel.spec:         "env" :
{"GUIX_PYTHONPATH":".guix-profile/lib/python3.9/site-packages/"}  - 
https://jupyter-client.readthedocs.io/en/stable/kernels.html#kernel-specs id="-x-evo-selection-start-marker">

Could you please adjust the package so that the kernel is able to find
the bash_kernel module ?

Thank you

Best,
Dan




[-- Attachment #1.2: Type: text/html, Size: 1922 bytes --]

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 7745 bytes --]

                 reply	other threads:[~2022-09-07 16:36 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=00f155bff5d649a49a129e47a4e2851f490887b3.camel@mdc-berlin.de \
    --to=dan.munteanu@mdc-berlin.de \
    --cc=57648@debbugs.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.
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).