jupyter-qtconsole, turtle, and Xfce: unresponsive turtle console

[Jerome BENOIT]

Hello Debian Users,

I am playing with jupyter-qtconsole in Xfce. Debian is Debain version 11.4.
When I launch a turple from the jupyter-qtconsole, I get a turtle console as 
expected.
And I can move the turtle around. However, when I switch to another workspace 
and
then come back to the workspace having the turtle console, it appears that the 
turtle
console is unresponsive: the frame is present, but the inside contain random 
stuff
from other workspaces.
When I do the same directly from python3, the turtle console behaves as 
expected.

How can we fix this issue ?

The python3 code is:

import turtle
bob=turtle.Turtle() ## here a turtle console pop up
bob.fd(100) ## and so forth.


Thanks in advance,
best wishes,
Jerome

Re: jupyter-notebook and bullseye

[David Wright]

On Fri 31 Dec 2021 at 15:07:39 (-0700), D. R. Evans wrote:
> Reco wrote on 12/31/21 1:47 PM:
> 
> > > That was certainly a help (although I wonder why it was necessary for me 
> > > to do that manually),
> > 
> > It's official Debian policy now, believe it or not.
> > python 2.x is /usr/bin/python2.
> > python 3.x is /usr/bin/python3.
> > 
> > If the user really wants /usr/bin/python the user should install
> > python-is-python2 or python-is-python3. And these two packages conflict
> > with each other.
> 
> Once upon a time, not really that long ago, Debian seemed to make very
> sensible decisions to keep everything stable and working across
> upgrades.

I don't understand: the exchange above seems to indicate that they've
done what you asked for, to provide an upgrade path for your Python2
software that is now one year beyond EOL.

> In the past few years, however, I find myself shaking my
> head and wondering "what were they thinking?" It's not that some of
> the things they've done are necessarily *wrong* per se, but they have
> certainly been a lot more experimental than one wants in an
> environment that one expects to keep working properly across upgrades;
> it seems that somehow the importance of keeping the users' systems
> functioning as one hopes they will is now a much lower priority than
> it used to be.

I see no evidence of that. The Release Notes for buster gave
notice of the end of Python2 support, and so the provision of
python-is-python2 might be seen as something of a plus.

There's not much point in blaming Debian for the demise of Python2.
Were Debian to ignore the lack of security support and just observe
the consequences, that's what I'd call "being experimental".

> But it certainly would be nice to at least be able to use my old
> jupyter notebooks, even if it's unlikely that I'll create any new
> ones.

> > Judging from [1], you're required to reinstall all these "jupyter
> > kernels", because what you have was installed for python2, but what you
> > need is to install them for python3.

> That's probably a good bet. I don't remember how any of those kernels
> got installed [I thought that all except the sos kernel were from
> debian repositories, but my memory might be faulty], so I'll have to
> search around and see what I can dig up. The evidence to hand does
> seem to suggest that they don't auto-upgrade and therefore need to be
> upgraded manually somehow.

One might assume that others have tackled this conversion process,
probably a few years ago. I certainly get google hits that look as if
that's what people have done, though I can't be certain as I don't use
Jupyter. (I typed   convert python2 python3 jupyter.) Perhaps it's
worth backing up your data and then trying out some of these
processes. I can't see Python2 sticking around for ever.

Alternatively, you could just install an older Debian version onto
a junk machine, and keep it safely away from the connected world.

Cheers,
David.

Re: jupyter-notebook and bullseye

[Nicholas Geovanis]

On Fri, Dec 31, 2021, 4:08 PM D. R. Evans  wrote:

> ..
>
> Pretty wise; I think. I was sucked in a bit about the hype that surrounds
> it
> and put in quite a bit of effort to build some useful notebooks a few
> years
> ago. But now I find that it's pretty much like the majority of experiments
> I've tried over the years: it looks nifty, and doubtless some people find
> it
> useful, but for me it's too fragile and ultimately the cost in time isn't
> worth the possible benefit.
>

For better and for worse, it has become the communication medium for
machine learning and knowledge engineering. Lots of open-source notebooks
are distributed.

.
>

Re: jupyter-notebook and bullseye

[Dan Ritter]

D. R. Evans wrote: 
> > If the user really wants /usr/bin/python the user should install
> > python-is-python2 or python-is-python3. And these two packages conflict
> > with each other.
> 
> Once upon a time, not really that long ago, Debian seemed to make very
> sensible decisions to keep everything stable and working across upgrades. In
> the past few years, however, I find myself shaking my head and wondering
> "what were they thinking?"

95% of the time, making the best available choices in a world
where nobody else cares.

4% of the time, shrugging and saying "everybody else is doing
it".

1% of the time, inexplicable.

I think that these ratios are better than other distributions,
which is why I keep using and recommending Debian.


> It's not that some of the things they've done are
> necessarily *wrong* per se, but they have certainly been a lot more
> experimental than one wants in an environment that one expects to keep
> working properly across upgrades; it seems that somehow the importance of
> keeping the users' systems functioning as one hopes they will is now a much
> lower priority than it used to be.

You can't have a bug-free system, you can't have a stable system, and
you can't have an up-to-date system. You can lean closer to any two of
those by getting further from the third.

In general, each Debian stable=>stable upgrade has been less disruptive
than the previous one. A distro can go to a rolling release, but that
means that either something is broken all the time or there is only one
canonical way to do things: a notional Debian "Luxo" rolling release that
tried to produce a stabilized stream from testing would require twice
as many Debian Developers, or an 85% cut in the number of packages,
or perhaps both.

-dsr-

Re: jupyter-notebook and bullseye

[D. R. Evans]

Reco wrote on 12/31/21 1:47 PM:



That was certainly a help (although I wonder why it was necessary for me to do 
that manually),


It's official Debian policy now, believe it or not.
python 2.x is /usr/bin/python2.
python 3.x is /usr/bin/python3.

If the user really wants /usr/bin/python the user should install
python-is-python2 or python-is-python3. And these two packages conflict
with each other.



Once upon a time, not really that long ago, Debian seemed to make very 
sensible decisions to keep everything stable and working across upgrades. In 
the past few years, however, I find myself shaking my head and wondering "what 
were they thinking?" It's not that some of the things they've done are 
necessarily *wrong* per se, but they have certainly been a lot more 
experimental than one wants in an environment that one expects to keep working 
properly across upgrades; it seems that somehow the importance of keeping the 
users' systems functioning as one hopes they will is now a much lower priority 
than it used to be.



but ultimately I am still unable to do anything.


I'm not familiar with jupyter and I'm not using it.



Pretty wise; I think. I was sucked in a bit about the hype that surrounds it 
and put in quite a bit of effort to build some useful notebooks a few years 
ago. But now I find that it's pretty much like the majority of experiments 
I've tried over the years: it looks nifty, and doubtless some people find it 
useful, but for me it's too fragile and ultimately the cost in time isn't 
worth the possible benefit.


But it certainly would be nice to at least be able to use my old jupyter 
notebooks, even if it's unlikely that I'll create any new ones.




Judging from [1], you're required to reinstall all these "jupyter
kernels", because what you have was installed for python2, but what you
need is to install them for python3.

But then again, I could be wrong. Sorry, cannot help you further.


That's probably a good bet. I don't remember how any of those kernels got 
installed [I thought that all except the sos kernel were from debian 
repositories, but my memory might be faulty], so I'll have to search around 
and see what I can dig up. The evidence to hand does seem to suggest that they 
don't auto-upgrade and therefore need to be upgraded manually somehow.


Thank you for taking the time to share your thoughts, especially as you don't 
use jupyter yourself.


  Doc

--
Web:  http://enginehousebooks.com/drevans

Re: jupyter-notebook and bullseye

[Reco]

Hi.

On Fri, Dec 31, 2021 at 01:35:47PM -0700, D. R. Evans wrote:
> Reco wrote on 12/17/21 6:10 AM:
> > Hi.
> > 
> > On Thu, Dec 16, 2021 at 12:43:51PM -0700, D. R. Evans wrote:
> > > FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/python'
> > ...
> > > Can someone suggest how I might get back to the fully-working set of 
> > > kernels that I had in buster?
> > 
> > Try this:
> > 
> > apt install python-is-python3
> 
> Thank you very much.
> 
> That was certainly a help (although I wonder why it was necessary for me to 
> do that manually),

It's official Debian policy now, believe it or not.
python 2.x is /usr/bin/python2.
python 3.x is /usr/bin/python3.

If the user really wants /usr/bin/python the user should install
python-is-python2 or python-is-python3. And these two packages conflict
with each other.

> but ultimately I am still unable to do anything.

I'm not familiar with jupyter and I'm not using it.

What I do know is:
a) /usr/bin/python was python 2.x in Debian 10.
b) Python 2.x and python 3.x modules are not compatible nor they are
interchangeable.

Judging from [1], you're required to reinstall all these "jupyter
kernels", because what you have was installed for python2, but what you
need is to install them for python3.

But then again, I could be wrong. Sorry, cannot help you further.

Reco

[1] https://github.com/takluyver/bash_kernel

Re: jupyter-notebook and bullseye

[D. R. Evans]

Reco wrote on 12/17/21 6:10 AM:

Hi.

On Thu, Dec 16, 2021 at 12:43:51PM -0700, D. R. Evans wrote:

FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/python'

...

Can someone suggest how I might get back to the fully-working set of kernels 
that I had in buster?


Try this:

apt install python-is-python3



Thank you very much.

That was certainly a help (although I wonder why it was necessary for me to do 
that manually), but ultimately I am still unable to do anything.


"jupyter kernelspec list" now looks better:



[ZB:jupyter] jupyter kernelspec list
Available kernels:
  ir  /home/n7dr/.local/share/jupyter/kernels/ir
  markdown/home/n7dr/.local/share/jupyter/kernels/markdown
  bash/usr/local/share/jupyter/kernels/bash
  gnuplot /usr/local/share/jupyter/kernels/gnuplot
  sos /usr/local/share/jupyter/kernels/sos
  python3 /usr/share/jupyter/kernels/python3
[ZB:jupyter]



But if I actually run jupyter-notebook on a known-good .ipynb file I get the 
following:




[ZB:jupyter] jn CQ*
[I 13:22:37.809 NotebookApp] Loading IPython parallel extension
[I 13:22:37.824 NotebookApp] Serving notebooks from local directory: 
/home/n7dr/notebooks/jupyter

[I 13:22:37.824 NotebookApp] Jupyter Notebook 6.2.0 is running at:
[I 13:22:37.824 NotebookApp] 
http://localhost:/?token=5e06127359465bc598e53eb5b48ef202592e96e3a1fe4ba7
[I 13:22:37.824 NotebookApp]  or 
http://127.0.0.1:/?token=5e06127359465bc598e53eb5b48ef202592e96e3a1fe4ba7
[I 13:22:37.825 NotebookApp] Use Control-C to stop this server and shut down 
all kernels (twice to skip confirmation).

[C 13:22:42.319 NotebookApp]

To access the notebook, open this file in a browser:

file:///home/n7dr/.local/share/jupyter/runtime/nbserver-2497406-open.html
Or copy and paste one of these URLs:

http://localhost:/?token=5e06127359465bc598e53eb5b48ef202592e96e3a1fe4ba7
 or 
http://127.0.0.1:/?token=5e06127359465bc598e53eb5b48ef202592e96e3a1fe4ba7
[W 13:22:50.477 NotebookApp] 404 GET 
/nbextensions/widgets/notebook/js/extension.js?v=20211231132234 (127.0.0.1) 
96.38ms referer=http://localhost:/notebooks/CQ%20WW.ipynb
[I 13:22:51.078 NotebookApp] 302 GET /notebooks/activity-160.png (127.0.0.1) 
0.67ms
[I 13:22:51.171 NotebookApp] 302 GET /notebooks/2017-ALL.png (127.0.0.1) 
0.61ms
[I 13:22:51.394 NotebookApp] 302 GET /notebooks/cq-ww-qso-nlogs-a-u.png 
(127.0.0.1) 0.62ms
[I 13:22:51.456 NotebookApp] 302 GET /notebooks/cq-ww-qso-percentiles.png 
(127.0.0.1) 0.64ms
[I 13:22:51.576 NotebookApp] Kernel started: 
9636f23d-6e5c-4ce6-931a-f0844f8876e5, name: bash

/usr/bin/python: No module named bash_kernel
[I 13:22:54.576 NotebookApp] KernelRestarter: restarting kernel (1/5), new 
random ports

/usr/bin/python: No module named bash_kernel
[I 13:22:57.590 NotebookApp] KernelRestarter: restarting kernel (2/5), new 
random ports

/usr/bin/python: No module named bash_kernel
[I 13:23:00.598 NotebookApp] KernelRestarter: restarting kernel (3/5), new 
random ports

/usr/bin/python: No module named bash_kernel
[I 13:23:03.605 NotebookApp] KernelRestarter: restarting kernel (4/5), new 
random ports

/usr/bin/python: No module named bash_kernel
[W 13:23:06.621 NotebookApp] KernelRestarter: restart failed
[W 13:23:06.621 NotebookApp] Kernel 9636f23d-6e5c-4ce6-931a-f0844f8876e5 died, 
removing from map.
[W 13:23:12.691 NotebookApp] Replacing stale connection: 
9636f23d-6e5c-4ce6-931a-f0844f8876e5:1820effccd3749579998b085be46704b
[W 13:23:34.746 NotebookApp] Replacing stale connection: 
9636f23d-6e5c-4ce6-931a-f0844f8876e5:1820effccd3749579998b085be46704b
[W 13:23:51.683 NotebookApp] Timeout waiting for kernel_info reply from 
9636f23d-6e5c-4ce6-931a-f0844f8876e5
[E 13:23:51.686 NotebookApp] Error opening stream: HTTP 404: Not Found (Kernel 
does not exist: 9636f23d-6e5c-4ce6-931a-f0844f8876e5)
[W 13:23:51.689 NotebookApp] 404 GET 
/api/kernels/9636f23d-6e5c-4ce6-931a-f0844f8876e5/channels?session_id=1820effccd3749579998b085be46704b 
(127.0.0.1): Kernel does not exist: 9636f23d-6e5c-4ce6-931a-f0844f8876e5
[W 13:23:51.690 NotebookApp] 404 GET 
/api/kernels/9636f23d-6e5c-4ce6-931a-f0844f8876e5/channels?session_id=1820effccd3749579998b085be46704b 
(127.0.0.1) 39005.31ms referer=None
[W 13:23:51.690 NotebookApp] 404 GET 
/api/kernels/9636f23d-6e5c-4ce6-931a-f0844f8876e5/channels?session_id=1820effccd3749579998b085be46704b 
(127.0.0.1): Kernel does not exist: 9636f23d-6e5c-4ce6-931a-f0844f8876e5
[W 13:23:51.691 NotebookApp] 404 GET 
/api/kernels/9636f23d-6e5c-4ce6-931a-f0844f8876e5/channels?session_id=1820effccd3749579998b085be46704b 
(127.0.0.1) 16950.43ms referer=None
[W 13:23:55.701 NotebookApp] Replacing stale connection: 
9636f23d-6e5c-4ce6-931a-f0844f8876e5:1820effccd3749579998b085be46704b
[W 13:24:23.733 NotebookApp] Replacing stale connection: 
9636f23d-6e5c-4ce6-931a-f0844f8876e5:1820effccd3749579998b085be46704b




And in the brow

Re: jupyter-notebook and bullseye

[Reco]

Hi.

On Thu, Dec 16, 2021 at 12:43:51PM -0700, D. R. Evans wrote:
> FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/python'
...
> Can someone suggest how I might get back to the fully-working set of kernels 
> that I had in buster?

Try this:

apt install python-is-python3

Reco

jupyter-notebook and bullseye

[D. R. Evans]

I don't use jupyter-notebook often, so I only just discovered that I am 
encountering a problem with it following my upgrade from buster to bullseye a 
couple of months ago. It worked fine on buster, and I have changed nothing 
related to jupyter since the upgrade.


When jupyter-notebook starts the browser, I see a big red "kernel error" 
button, and when I press it, the following pops up:




Traceback (most recent call last):
   File "/usr/lib/python3/dist-packages/tornado/web.py", line 1704, in _execute
 result = await result
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/handlers.py", line 
69, in post

 model = yield maybe_future(
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/sessionmanager.py", 
line 88, in create_session
 kernel_id = yield self.start_kernel_for_session(session_id, path, name, 
type, kernel_name)

   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 769, in run
 yielded = self.gen.throw(*exc_info)  # type: ignore
   File 
"/usr/lib/python3/dist-packages/notebook/services/sessions/sessionmanager.py", 
line 100, in start_kernel_for_session

 kernel_id = yield maybe_future(
   File "/usr/lib/python3/dist-packages/tornado/gen.py", line 762, in run
 value = future.result()
   File 
"/usr/lib/python3/dist-packages/notebook/services/kernels/kernelmanager.py", 
line 176, in start_kernel
 kernel_id = await maybe_future(self.pinned_superclass.start_kernel(self, 
**kwargs))
   File 
"/usr/lib/python3/dist-packages/jupyter_client/multikernelmanager.py", line 
185, in start_kernel

 km.start_kernel(**kwargs)
   File "/usr/lib/python3/dist-packages/jupyter_client/manager.py", line 313, 
in start_kernel

 self.kernel = self._launch_kernel(kernel_cmd, **kw)
   File "/usr/lib/python3/dist-packages/jupyter_client/manager.py", line 222, 
in _launch_kernel

 return launch_kernel(kernel_cmd, **kw)
   File "/usr/lib/python3/dist-packages/jupyter_client/launcher.py", line 
134, in launch_kernel

 proc = Popen(cmd, **kwargs)
   File "/usr/lib/python3.9/subprocess.py", line 951, in __init__
 self._execute_child(args, executable, preexec_fn, close_fds,
   File "/usr/lib/python3.9/subprocess.py", line 1823, in _execute_child
 raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] No such file or directory: '/usr/bin/python'

-

It is certainly true that that file does not exist, but something is obviously 
telling jupyter to look for it. So something about the jupyter configuration 
seems to have been hosed by the upgrade.


The command "jupyter kernelspec list" produces:



[ZB:~] jupyter kernelspec list
-bash: /home/n7dr/.local/bin/jupyter: /usr/bin/python: bad interpreter: No 
such file or directory

[ZB:~]



In buster I had perhaps half a dozen kernels available (and they all worked).

Can someone suggest how I might get back to the fully-working set of kernels 
that I had in buster?


  Doc

--
Web:  http://enginehousebooks.com/drevans

Re: Jupyter

[Nicolas FRANCOIS]

Le Wed, 24 Jun 2020 23:00:22 +0200 (CEST),
l0f...@tuta.io a écrit :

> 24 juin 2020 à 21:43 de nicolas.franc...@free.fr:
> 
> > Et ? Qu'est-ce que j'aurais du faire ? J'ai installé les paquets
> > avec apt-get. Les commandes systemd sont exécutées en tant que
> > super-utilisateur.
> >  
> Comme indiqué sur le Wiki Debian, simplement :
> systemctl --user enable jupyter-notebook.service
> systemctl --user start jupyter-notebook.service
> 
> Ça marche toujours pas ?

Bin si, ça fonctionne. J'avais complètement zappé l'option --user !
Sans doute parce que je ne savais même pas qu'on pouvait lancer une
commande systemctl en tant que simple utilisateur...

On en apprend tous les jours !

Merci pour ta persévérance :-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgp4myqQVmTyp.pgp
Description: Signature digitale OpenPGP

Re: Jupyter

[l0f4r0]

24 juin 2020 à 21:43 de nicolas.franc...@free.fr:

> Et ? Qu'est-ce que j'aurais du faire ? J'ai installé les paquets avec
> apt-get. Les commandes systemd sont exécutées en tant que
> super-utilisateur.
>
Comme indiqué sur le Wiki Debian, simplement :
systemctl --user enable jupyter-notebook.service
systemctl --user start jupyter-notebook.service

Ça marche toujours pas ?

l0f4r0

Re: Jupyter

[Nicolas FRANCOIS]

Le Wed, 24 Jun 2020 21:08:19 +0200 (CEST),
l0f...@tuta.io a écrit :

> Bonjour,
> 
> 24 juin 2020 à 13:25 de nicolas.franc...@free.fr:
> 
> > Salut.
> >
> > J'ai installé sur mon ordinateur Jupyter (jupyter, jupyter-client,
> > jupyter-console, jupyter-core, jupyter-notebook, jupyter-qtconsole,
> > ipython), et je voudrais que le service soit lancé automatiquement
> > au démarrage du système.
> >
> > Sur la page https://wiki.debian.org/Jupyter, il est dit qu'on peut
> > faire cela avec systemd :
> > systemctl --user enable jupyter-notebook.service
> > systemctl --user start jupyter-notebook.service
> >
> > Mais quand je tape la première ligne (ou la deuxième), j'obtiens
> > ceci :
> >
> > nico@Gaston:~$ sudo systemctl enable jupyter-notebook.service
> > Failed to enable unit: Unit file jupyter-notebook.service does not
> > exist.
> >
> > Pourtant, j'ai ce qu'il faut, il me semble :
> > nico@Gaston:~$ locate jupyter-notebook.service
> > /usr/lib/systemd/user/jupyter-notebook.service
> >
> > Je ne suis pas très à l'aise avec systemd. Faut-il que je copie ce
> > script à un endroit où systemd peut le trouver ?
> >
> > D'avance merci pour toute explication :-)
> >  
> Probablement parce que tu as tapé les commandes en tant que
> super-administrateur via sudo et que tu n'as pas utilisé le switch
> --user ? La preuve, ton service est dans /usr/lib/systemd/user/

Et ? Qu'est-ce que j'aurais du faire ? J'ai installé les paquets avec
apt-get. Les commandes systemd sont exécutées en tant que
super-utilisateur.

Faut-il que je déplace le fichier du service autre part ? Si oui, où ?

D'avance merci. Et désolé pour la direction incorrecte, comme je le
signale dans la mailing liste anglophone, j'ai réglé mon client Claws
pour que les messages envoyés quand je suis dans ce dossier soient
dirigés vers la liste francophone... sauf que j'ai du me gourancer
quelque part :-(

\bye
 
> NB : je mets en Cc la ML debian-user-french
> 
> Bien cordialement,
> l0f4r0
> 



-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpSpktPZgB5q.pgp
Description: Signature digitale OpenPGP

Re: Jupyter

[Nicolas FRANCOIS]

Le Wed, 24 Jun 2020 13:47:25 +0200,
john doe  a écrit :

> This is an English mailing list, you might be better off in a French
> one! :)

Oups, sorry, I thought I had setup my Claws Mail client to post on the
french list when I'm in the french list directory.

Sorry for the noise.
 
\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpUNQ2hVYdVD.pgp
Description: Signature digitale OpenPGP

Re: Jupyter

[l0f4r0]

Bonjour,

24 juin 2020 à 13:25 de nicolas.franc...@free.fr:

> Salut.
>
> J'ai installé sur mon ordinateur Jupyter (jupyter, jupyter-client,
> jupyter-console, jupyter-core, jupyter-notebook, jupyter-qtconsole,
> ipython), et je voudrais que le service soit lancé automatiquement au
> démarrage du système.
>
> Sur la page https://wiki.debian.org/Jupyter, il est dit qu'on peut
> faire cela avec systemd :
> systemctl --user enable jupyter-notebook.service
> systemctl --user start jupyter-notebook.service
>
> Mais quand je tape la première ligne (ou la deuxième), j'obtiens ceci :
>
> nico@Gaston:~$ sudo systemctl enable jupyter-notebook.service
> Failed to enable unit: Unit file jupyter-notebook.service does not
> exist.
>
> Pourtant, j'ai ce qu'il faut, il me semble :
> nico@Gaston:~$ locate jupyter-notebook.service
> /usr/lib/systemd/user/jupyter-notebook.service
>
> Je ne suis pas très à l'aise avec systemd. Faut-il que je copie ce
> script à un endroit où systemd peut le trouver ?
>
> D'avance merci pour toute explication :-)
>
Probablement parce que tu as tapé les commandes en tant que 
super-administrateur via sudo et que tu n'as pas utilisé le switch --user ?
La preuve, ton service est dans /usr/lib/systemd/user/

NB : je mets en Cc la ML debian-user-french

Bien cordialement,
l0f4r0

Re: Jupyter

[tomas]

On Wed, Jun 24, 2020 at 01:25:51PM +0200, Nicolas FRANCOIS wrote:
> Salut.
> 
> J'ai installé sur mon ordinateur Jupyter (jupyter, jupyter-client,
> jupyter-console, jupyter-core, jupyter-notebook, jupyter-qtconsole,
> ipython), et je voudrais que le service soit lancé automatiquement au
> démarrage du système.

Comment avez-vous installé jupyter? Avec un paquet Debian?

> Sur la page https://wiki.debian.org/Jupyter, il est dit qu'on peut
> faire cela avec systemd :
> systemctl --user enable jupyter-notebook.service
> systemctl --user start jupyter-notebook.service
> 
> Mais quand je tape la première ligne (ou la deuxième), j'obtiens ceci :
> 
> nico@Gaston:~$ sudo systemctl enable jupyter-notebook.service
> Failed to enable unit: Unit file jupyter-notebook.service does not
> exist.
> 
> Pourtant, j'ai ce qu'il faut, il me semble :
> nico@Gaston:~$ locate jupyter-notebook.service
> /usr/lib/systemd/user/jupyter-notebook.service
> 
> Je ne suis pas très à l'aise avec systemd.

Moi non plus, désolé. En plus, mon Français est catastrophique.

Vous trouvez une liste francophone ici:

  https://lists.debian.org/debian-user-french/
  https://wiki.debian.org/fr/FrenchLists

salut
-- tomás


signature.asc
Description: Digital signature

Re: Jupyter

[john doe]

On 6/24/2020 1:25 PM, Nicolas FRANCOIS wrote:

Salut.

J'ai installé sur mon ordinateur Jupyter (jupyter, jupyter-client,
jupyter-console, jupyter-core, jupyter-notebook, jupyter-qtconsole,
ipython), et je voudrais que le service soit lancé automatiquement au
démarrage du système.

Sur la page https://wiki.debian.org/Jupyter, il est dit qu'on peut
faire cela avec systemd :
systemctl --user enable jupyter-notebook.service
systemctl --user start jupyter-notebook.service

Mais quand je tape la première ligne (ou la deuxième), j'obtiens ceci :

nico@Gaston:~$ sudo systemctl enable jupyter-notebook.service
Failed to enable unit: Unit file jupyter-notebook.service does not
exist.

Pourtant, j'ai ce qu'il faut, il me semble :
nico@Gaston:~$ locate jupyter-notebook.service
/usr/lib/systemd/user/jupyter-notebook.service

Je ne suis pas très à l'aise avec systemd. Faut-il que je copie ce
script à un endroit où systemd peut le trouver ?



This is an English mailing list, you might be better off in a French one! :)

--
John Doe

Jupyter

[Nicolas FRANCOIS]

Salut.

J'ai installé sur mon ordinateur Jupyter (jupyter, jupyter-client,
jupyter-console, jupyter-core, jupyter-notebook, jupyter-qtconsole,
ipython), et je voudrais que le service soit lancé automatiquement au
démarrage du système.

Sur la page https://wiki.debian.org/Jupyter, il est dit qu'on peut
faire cela avec systemd :
systemctl --user enable jupyter-notebook.service
systemctl --user start jupyter-notebook.service

Mais quand je tape la première ligne (ou la deuxième), j'obtiens ceci :

nico@Gaston:~$ sudo systemctl enable jupyter-notebook.service
Failed to enable unit: Unit file jupyter-notebook.service does not
exist.

Pourtant, j'ai ce qu'il faut, il me semble :
nico@Gaston:~$ locate jupyter-notebook.service
/usr/lib/systemd/user/jupyter-notebook.service

Je ne suis pas très à l'aise avec systemd. Faut-il que je copie ce
script à un endroit où systemd peut le trouver ?

D'avance merci pour toute explication :-)

\bye

-- 

Nicolas FRANCOIS  |  /\ 
http://nicolas.francois.free.fr   | |__|
  X--/\\
We are the Micro$oft.   _\_V
Resistance is futile.   
You will be assimilated. darthvader penguin


pgpK6IYQ8S7wm.pgp
Description: Signature digitale OpenPGP

Re: jupyter notebook immediately crashes with dead kernel

[D. R. Evans]

finn wrote on 11/07/2018 08:45 AM:
> Solution 1:
> sudo apt purge python3-ipykernel
> sudo apt install python3-ipykernel
> 
> Solution 2:
> OR, purge python-notebook package and install it again, it will automatically 
> install ipykernel package while resolving its dependency.
> sudo apt purge python-notebook
> sudo apt install python-notebook
> 
> Should fix you're issue.
> 

Nope. They don't. I reinstalled a few times while figuring out what the real
issue is.

> By the way, installing python-notebook from official debian 
> repo(http://deb.debian.org/debian) works for me without a singal error.
> 

Perhaps you don't have python2 installed. The official stable package looks
like it probably works fine if you don't have python2 installed.

But if you do have both official pythons installed from the stable
repositories, as I do, then /usr/bin/python points to python2 (at least it
does here) so that when jupyter tries to create a python3 notebook and
executes "python", then it executes python2,not python3, and hence there's a
rapid failure.

Easy to fix, per bug 913110, but it /is/ a bug.

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature

Re: jupyter notebook immediately crashes with dead kernel

[finn]

Solution 1:
sudo apt purge python3-ipykernel
sudo apt install python3-ipykernel

Solution 2:
OR, purge python-notebook package and install it again, it will automatically 
install ipykernel package while resolving its dependency.
sudo apt purge python-notebook
sudo apt install python-notebook

Should fix you're issue.

By the way, installing python-notebook from official debian 
repo(http://deb.debian.org/debian) works for me without a singal error.

‐‐‐ Original Message ‐‐‐
On Wednesday, November 7, 2018 7:59 PM, D. R. Evans  wrote:

> D. R. Evans wrote on 11/06/2018 07:56 AM:
>
> > D. R. Evans wrote on 11/05/2018 06:14 PM:
> >
> > > vipul kumar wrote on 11/05/2018 05:35 PM:
> > >
> > > > Run Jupyter-notebook from terminal. Send log report which you'll get on 
> > > > terminal while running jupyter-notebook.
> >
> > > [HN:~] jupyter-notebook
> > > [I 18:11:04.210 NotebookApp] Serving notebooks from local directory: 
> > > /home/n7dr
> > > [I 18:11:04.211 NotebookApp] 0 active kernels
> > > [I 18:11:04.211 NotebookApp] The Jupyter Notebook is running at:
> > > http://localhost:/
> > > [I 18:11:04.211 NotebookApp] Use Control-C to stop this server and shut 
> > > down
> > > all kernels (twice to skip confirmation).
> >
> > I see additional messages when I actually try to create the notebook 
> > (sorry; I
> > wasn't looking for those yesterday):
> >
> > HN:~] jupyter-notebook
> > [I 07:37:19.123 NotebookApp] Serving notebooks from local directory: 
> > /home/n7dr
> > [I 07:37:19.124 NotebookApp] 0 active kernels
> > [I 07:37:19.124 NotebookApp] The Jupyter Notebook is running at:
> > http://localhost:/
> > [I 07:37:19.124 NotebookApp] Use Control-C to stop this server and shut down
> > all kernels (twice to skip confirmation).
> > [I 07:37:29.629 NotebookApp] Creating new notebook in
> > [I 07:37:32.575 NotebookApp] Kernel started: 
> > 00f6d461-87f1-410e-9963-5f5db91602f3
> > /usr/bin/python: No module named ipykernel_launcher
> > [I 07:37:35.561 NotebookApp] KernelRestarter: restarting kernel (1/5)
> > /usr/bin/python: No module named ipykernel_launcher
> > [I 07:37:38.571 NotebookApp] KernelRestarter: restarting kernel (2/5)
> > /usr/bin/python: No module named ipykernel_launcher
> > [I 07:37:41.582 NotebookApp] KernelRestarter: restarting kernel (3/5)
> > /usr/bin/python: No module named ipykernel_launcher
> > [W 07:37:42.678 NotebookApp] Timeout waiting for kernel_info reply from
> > 00f6d461-87f1-410e-9963-5f5db91602f3
> > [I 07:37:44.592 NotebookApp] KernelRestarter: restarting kernel (4/5)
> > WARNING:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted
> > /usr/bin/python: No module named ipykernel_launcher
> > [W 07:37:47.604 NotebookApp] KernelRestarter: restart failed
> > [W 07:37:47.605 NotebookApp] Kernel 00f6d461-87f1-410e-9963-5f5db91602f3 
> > died,
> > removing from map.
> > ERROR:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted failed!
> > [W 07:37:47.654 NotebookApp] Kernel deleted before session
> > [W 07:37:47.656 NotebookApp] 410 DELETE
> > /api/sessions/56ef952c-800c-448f-baf0-857081b87abc (::1) 3.46ms
> > referer=http://localhost:/notebooks/Untitled4.ipynb?kernel_name=python3
> >
> > The strange thing here is:
> > /usr/bin/python: No module named ipykernel_launcher
> > Why is it running /usr/bin/python, which is a link to python2??
> >
> > HN:~] ls -al /usr/bin/python
> > lrwxrwxrwx 1 root root 9 Jan 24 2017 /usr/bin/python -> python2.7
> >
> > I would have thought that, since the package installed the ipython3 kernel 
> > for
> > jupyter, and when I try to create a notebook, it's python3 that is in the
> > "New" drop-down menu on the jupyter page, then it should be executing
> > /usr/bin/python3, not /usr/bin/python.
> > Is this perhaps an error in the packaging?
>
> This is now bug 913110:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913110
>
> The bug report includes a simple fix.
>
> Doc
>
> ---
>
> Web: http://enginehousebooks.com/drevans

Re: jupyter notebook immediately crashes with dead kernel

[D. R. Evans]

D. R. Evans wrote on 11/06/2018 07:56 AM:
> D. R. Evans wrote on 11/05/2018 06:14 PM:
>> vipul kumar wrote on 11/05/2018 05:35 PM:
>>> Run Jupyter-notebook from terminal. Send log report which you'll get on 
>>> terminal while running jupyter-notebook.
>>>
>>
> 
>>
>> [HN:~] jupyter-notebook
>> [I 18:11:04.210 NotebookApp] Serving notebooks from local directory: 
>> /home/n7dr
>> [I 18:11:04.211 NotebookApp] 0 active kernels
>> [I 18:11:04.211 NotebookApp] The Jupyter Notebook is running at:
>> http://localhost:/
>> [I 18:11:04.211 NotebookApp] Use Control-C to stop this server and shut down
>> all kernels (twice to skip confirmation).
>>
>> 
> 
> I see additional messages when I actually try to create the notebook (sorry; I
> wasn't looking for those yesterday):
> 
> 
> 
> HN:~] jupyter-notebook
> [I 07:37:19.123 NotebookApp] Serving notebooks from local directory: 
> /home/n7dr
> [I 07:37:19.124 NotebookApp] 0 active kernels
> [I 07:37:19.124 NotebookApp] The Jupyter Notebook is running at:
> http://localhost:/
> [I 07:37:19.124 NotebookApp] Use Control-C to stop this server and shut down
> all kernels (twice to skip confirmation).
> [I 07:37:29.629 NotebookApp] Creating new notebook in
> [I 07:37:32.575 NotebookApp] Kernel started: 
> 00f6d461-87f1-410e-9963-5f5db91602f3
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:35.561 NotebookApp] KernelRestarter: restarting kernel (1/5)
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:38.571 NotebookApp] KernelRestarter: restarting kernel (2/5)
> /usr/bin/python: No module named ipykernel_launcher
> [I 07:37:41.582 NotebookApp] KernelRestarter: restarting kernel (3/5)
> /usr/bin/python: No module named ipykernel_launcher
> [W 07:37:42.678 NotebookApp] Timeout waiting for kernel_info reply from
> 00f6d461-87f1-410e-9963-5f5db91602f3
> [I 07:37:44.592 NotebookApp] KernelRestarter: restarting kernel (4/5)
> WARNING:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted
> /usr/bin/python: No module named ipykernel_launcher
> [W 07:37:47.604 NotebookApp] KernelRestarter: restart failed
> [W 07:37:47.605 NotebookApp] Kernel 00f6d461-87f1-410e-9963-5f5db91602f3 died,
> removing from map.
> ERROR:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted failed!
> [W 07:37:47.654 NotebookApp] Kernel deleted before session
> [W 07:37:47.656 NotebookApp] 410 DELETE
> /api/sessions/56ef952c-800c-448f-baf0-857081b87abc (::1) 3.46ms
> referer=http://localhost:/notebooks/Untitled4.ipynb?kernel_name=python3
> 
> 
> 
> The strange thing here is:
>   /usr/bin/python: No module named ipykernel_launcher
> 
> Why is it running /usr/bin/python, which is a link to python2??
> 
> 
> 
> HN:~] ls -al /usr/bin/python
> lrwxrwxrwx 1 root root 9 Jan 24  2017 /usr/bin/python -> python2.7
> 
> 
> 
> I would have thought that, since the package installed the ipython3 kernel for
> jupyter, and when I try to create a notebook, it's python3 that is in the
> "New" drop-down menu on the jupyter page, then it should be executing
> /usr/bin/python3, not /usr/bin/python.
> 
> Is this perhaps an error in the packaging?

This is now bug 913110:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=913110

The bug report includes a simple fix.

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature

Re: jupyter notebook immediately crashes with dead kernel

[D. R. Evans]

D. R. Evans wrote on 11/05/2018 06:14 PM:
> vipul kumar wrote on 11/05/2018 05:35 PM:
>> Run Jupyter-notebook from terminal. Send log report which you'll get on 
>> terminal while running jupyter-notebook.
>>
>

> 
> [HN:~] jupyter-notebook
> [I 18:11:04.210 NotebookApp] Serving notebooks from local directory: 
> /home/n7dr
> [I 18:11:04.211 NotebookApp] 0 active kernels
> [I 18:11:04.211 NotebookApp] The Jupyter Notebook is running at:
> http://localhost:/
> [I 18:11:04.211 NotebookApp] Use Control-C to stop this server and shut down
> all kernels (twice to skip confirmation).
> 
> 

I see additional messages when I actually try to create the notebook (sorry; I
wasn't looking for those yesterday):



HN:~] jupyter-notebook
[I 07:37:19.123 NotebookApp] Serving notebooks from local directory: /home/n7dr
[I 07:37:19.124 NotebookApp] 0 active kernels
[I 07:37:19.124 NotebookApp] The Jupyter Notebook is running at:
http://localhost:/
[I 07:37:19.124 NotebookApp] Use Control-C to stop this server and shut down
all kernels (twice to skip confirmation).
[I 07:37:29.629 NotebookApp] Creating new notebook in
[I 07:37:32.575 NotebookApp] Kernel started: 
00f6d461-87f1-410e-9963-5f5db91602f3
/usr/bin/python: No module named ipykernel_launcher
[I 07:37:35.561 NotebookApp] KernelRestarter: restarting kernel (1/5)
/usr/bin/python: No module named ipykernel_launcher
[I 07:37:38.571 NotebookApp] KernelRestarter: restarting kernel (2/5)
/usr/bin/python: No module named ipykernel_launcher
[I 07:37:41.582 NotebookApp] KernelRestarter: restarting kernel (3/5)
/usr/bin/python: No module named ipykernel_launcher
[W 07:37:42.678 NotebookApp] Timeout waiting for kernel_info reply from
00f6d461-87f1-410e-9963-5f5db91602f3
[I 07:37:44.592 NotebookApp] KernelRestarter: restarting kernel (4/5)
WARNING:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted
/usr/bin/python: No module named ipykernel_launcher
[W 07:37:47.604 NotebookApp] KernelRestarter: restart failed
[W 07:37:47.605 NotebookApp] Kernel 00f6d461-87f1-410e-9963-5f5db91602f3 died,
removing from map.
ERROR:root:kernel 00f6d461-87f1-410e-9963-5f5db91602f3 restarted failed!
[W 07:37:47.654 NotebookApp] Kernel deleted before session
[W 07:37:47.656 NotebookApp] 410 DELETE
/api/sessions/56ef952c-800c-448f-baf0-857081b87abc (::1) 3.46ms
referer=http://localhost:/notebooks/Untitled4.ipynb?kernel_name=python3



The strange thing here is:
  /usr/bin/python: No module named ipykernel_launcher

Why is it running /usr/bin/python, which is a link to python2??



HN:~] ls -al /usr/bin/python
lrwxrwxrwx 1 root root 9 Jan 24  2017 /usr/bin/python -> python2.7



I would have thought that, since the package installed the ipython3 kernel for
jupyter, and when I try to create a notebook, it's python3 that is in the
"New" drop-down menu on the jupyter page, then it should be executing
/usr/bin/python3, not /usr/bin/python.

Is this perhaps an error in the packaging?

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature

Re: jupyter notebook immediately crashes with dead kernel

[D. R. Evans]

vipul kumar wrote on 11/05/2018 05:35 PM:
> Run Jupyter-notebook from terminal. Send log report which you'll get on 
> terminal while running jupyter-notebook.
> 
> 



[W 18:07:15.047 NotebookApp] Widgets are unavailable. On Debian, notebook
support for widgets is provided by the package
jupyter-nbextension-jupyter-js-widgets
[I 18:07:15.100 NotebookApp] Serving notebooks from local directory: /home/n7dr
[I 18:07:15.100 NotebookApp] 0 active kernels
[I 18:07:15.100 NotebookApp] The Jupyter Notebook is running at:
http://localhost:/
[I 18:07:15.100 NotebookApp] Use Control-C to stop this server and shut down
all kernels (twice to skip confirmation)



I was going to add the widget support after the basic notebook is working, but
installed jupyter-nbextension-jupyter-js-widgets anyway and tried again:

----

[HN:~] jupyter-notebook
[I 18:11:04.210 NotebookApp] Serving notebooks from local directory: /home/n7dr
[I 18:11:04.211 NotebookApp] 0 active kernels
[I 18:11:04.211 NotebookApp] The Jupyter Notebook is running at:
http://localhost:/
[I 18:11:04.211 NotebookApp] Use Control-C to stop this server and shut down
all kernels (twice to skip confirmation).



So the warning message goes away (as expected) but the behaviour is unchanged:
the kernel still dies when I try to create a notebook.

  Doc

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature

Re: jupyter notebook immediately crashes with dead kernel

[vipul kumar]

Run Jupyter-notebook from terminal. Send log report which you'll get on 
terminal while running jupyter-notebook.


Sent with ProtonMail Secure Email.

‐‐‐ Original Message ‐‐‐
On Tuesday, November 6, 2018 5:30 AM, D. R. Evans  wrote:

> Running current debian stable (64-bit).
>
> I installed the jupyter-notebook package (which caused several other packages
> associated with python3 to be installed).
>
> There was no indication of any problems with the installation, and I didn't
> see any messages suggesting that anything else needs to be done to run 
> jupyter.
>
> But when I run the application and try to create a new notebook using File |
> New Notebook | Python3 on the web page
> http://localhost:/notebooks/Untitled1.ipynb?kernel_name=python3, the
> python3 kernel will not start and I get a message saying that it has died.
> Attempts to restart the kernel produce the same result.
>
> What else do I need to do to get this package to work? Or is there somewhere
> on the system where I can find a more useful error message?
>
> Doc Evans
>
> 
>
> Web: http://enginehousebooks.com/drevans

jupyter notebook immediately crashes with dead kernel

[D. R. Evans]

Running current debian stable (64-bit).

I installed the jupyter-notebook package (which caused several other packages
associated with python3 to be installed).

There was no indication of any problems with the installation, and I didn't
see any messages suggesting that anything else needs to be done to run jupyter.

But when I run the application and try to create a new notebook using File |
New Notebook | Python3 on the web page
http://localhost:/notebooks/Untitled1.ipynb?kernel_name=python3, the
python3 kernel will not start and I get a message saying that it has died.
Attempts to restart the kernel produce the same result.

What else do I need to do to get this package to work? Or is there somewhere
on the system where I can find a more useful error message?

  Doc Evans

-- 
Web:  http://enginehousebooks.com/drevans



signature.asc
Description: OpenPGP digital signature