Open route2021 opened 2 years ago
I don't think I'll ever be able to make it work. It requires functionalities that are not available, and that I don't know how to emulate.
I disabled the debugger extension in jupyterlab. That will prevent confusing the users.
What works very well ist the JupyterLab Terminal for a given Notebook (right click on tab caption), it can almost always replace a dedicated Debugger for me. But it would be great to start carnets as jupyterlab from the beginning, instead of opening the retrolab and then the view-menu, especially when you work with many open Applications in the Background, there is the occasional crash and then it would be nice to just get the lab immediatly. That said, great work!
Great suggestion; I'll think about it. There is the risk of having too many notebooks opening at startup.
Perhaps the latest k Notebooks perhaps, if that is managable? Thanks for the reply! Carnets let me do real work, i use it at the moment to analyze a Database from Children, who were born in Berlin from 2017 to 2020 to detect changes in preterm-patterns with regard to Sars-Cov-II, thats 180000 Rows with >100 Columns, which are all handled with ease. Better than Juno.
Yours TR
Von meinem iPad gesendet
Am 26.04.2022 um 13:03 schrieb Nicolas Holzschuch @.***>:
Great suggestion; I'll think about it. There is the risk of having too many notebooks opening at startup.
— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.
Problem is, the jupyterlab debugger does not work in Carnets, but scipy does. Now a-shell runs a full jupyterlab, but no scipy …
I'm not sure the debugger can actually work in either a-Shell or Carnets (there are too many system layers missing), that's why I explicitly disabled it in Carnets. If you can actually make it run in a-Shell, I'll reconsider.
Hi, the debugger doesn't work on jupyterlab.