From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Hinsen Subject: bug#30921: Jupyter uses the wrong Python. Date: Sun, 25 Mar 2018 11:39:23 +0200 Message-ID: References: <87tvt5ixmc.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38925) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1f028F-0002d7-Se for bug-guix@gnu.org; Sun, 25 Mar 2018 05:40:08 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1f028A-0001CW-SK for bug-guix@gnu.org; Sun, 25 Mar 2018 05:40:07 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:44200) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1f028A-0001CQ-Iy for bug-guix@gnu.org; Sun, 25 Mar 2018 05:40:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1f028A-0004SW-6b for bug-guix@gnu.org; Sun, 25 Mar 2018 05:40:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87tvt5ixmc.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus , Fis Trivial Cc: 30921@debbugs.gnu.org Ricardo Wurmus writes: > I wonder if that=E2=80=99s 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? Yes. Installed kernels are normally under $prefix/share/jupyter/kernels. A standard installation of Jupyter via PyPI also installs a kernel for the same Python interpreter that is used for Jupyter. Additional kernels can then be installed afterwards. Fis Trivial writes: > 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 You could run jupyter kernelspec list to see which kernels Jupyter actually uses. Konrad.