Closed ubaldot closed 1 year ago
There is no reason for this to happen in JupyterConsole and not in notebook. Can you reproduce this with notebook ? It might be an ipykernel issue, but it's starting to be outside of my area of expertise.
Tried with both notebook
and jupyter-lab
. None worked. Below a screenshot from jupyter-lab
.
Perhaps this issue should be linked to notebook
- jupyter-lab
issue trackers?
There is no reason for this to happen in JupyterConsole and not in notebook. Can you reproduce this with notebook ? It might be an ipykernel issue, but it's starting to be outside of my area of expertise.
I am not sure if ipython
or jupyter console --kernel=python3
use the same ipykernel
, but if it is, then the problem is in most likely on jupyter
side than ipykernel
.
I tried to run the example script from a ipython
console (no jupyter) and I had no problems. Everything works as expected.
So $ ipython
does not use ipykernel
, the main big difference between $ ipython
and other things is that ipykernel use threads and eventloops which are likely to break eventloop integrations. So if it fails on both console and lab then it is most likely a ipykernel (maybe IPython issue).
I've opened https://github.com/ipython/ipykernel/issues/1124 upstream. Closing here.
Output of
%matplotlib osx
give the following error message:I tried to run %matplotlib` both in a IPython and a Jupyter console, getting the following outputs:
Using matplotlib backend: MacOSX
(IPython)Using matplotlib backend: <object object at 0x104853730>
(Jupyter console)the consequence is that plots in IPython are interactive whereas plots in Jupyter console are rendered as a simple
.png
. Example code follows if you want to test:I am running
Jupyter console 6.6.3, Python 3.10.8, IPython 8.12.0
withpyqt 5.51.7
installed throughconda
on Mac Os Ventura.