Kernel misses autoreload IPython extension

[SchraivogelS]

Hi there,
first of all thanks for the jupyter notebook extension for 3DSlicer.
It allows for streamlined data processing and reproducible workflows.

Slicer kernel seems to miss autoreload extension, which is a handy feature within jupyter notebooks.

%load_ext autoreload
causes AttributeError: 'kernel.XInteractiveShell' object has no attribute 'events'

[lassoan]

We use xeus-python kernel, which might have not implemented this yet - see the discussion here:

jupyter-xeus/xeus-python#63 (comment)

Could you ask for clarification either in that issue or creating a new one and report here what you find out?

If it is fixed/implemented recently then we may just need to update the xeus-python kernel version in SlicerJupyter.

[SchraivogelS]

They added a bunch of magics at the beginning of this year:
https://github.com/jupyter-xeus/xeus-python/blob/fc09e25d882e62bf72cc3ae6644b29cadd174fb8/notebooks/xeus-magics.ipynb

Just installed xeus-python 0.12.5 in a fresh conda env along with python 3.9.6 and autoreload extension is available.
Is an update feasible?

[lassoan]

I've tried to update but recent xeus-python versions require IPython>=7.21, but the last IPython version for Python-3.6 is IPython-7.15. We need to wait until Slicer core is updated to at least Python-3.7 - see Slicer/Slicer#5014.

[SchraivogelS]

Ok, thanks for checking. Am 09.07.2021 um 03:48 schrieb Andras Lasso ***@***.***>:  I've tried to update but recent xeus-python versions require IPython>=7.21, but the last IPython version for Python-3.6 is IPython-7.15. We need to wait until Slicer core is updated to at least Python-3.7 - see Slicer/Slicer#5014<Slicer/Slicer#5014>. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#62 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AUBC2JDXCMBRGBIG5CSHPKLTWZIORANCNFSM5AAQW4QA>.

[lassoan]

We have updated Slicer's Python some time ago and can use the latest xeus-python, so hopefully the problem is now fixed.