JupyterLab 4.0
blog.jupyter.org
JupyterLab 4.0
1–10 of 199 posts
Re: JupyterLab 4.0
#2For now, I need jupytext (which is a great extension), so then I stay with v3.6 until jupytext is resolved.
For this announcement - or in the changelog - it would be great to know why it is a major version bump - what is the major compatibility change?
Re: JupyterLab 4.0
#3Even a simple improvement like remembering the sizes of various subpanels in the debugger sidebar will make me feel like I am not pulling teeth when I use it.
And don't get me started on inspecting the value of variables. If you are looking for more than an object within an object, you might as well go back to print statements.
Re: JupyterLab 4.0
#4Anyone know about compatibility with existing notebooks? Presumably stellar, right? For now, I need jupytext (which is a great extension), so then I stay with v3.6 until jupytext is resolved. For this announcement - or in the changelog - it would be great to know why it is a major version bump - what is the major compatibility change?
P.S. Juptext is a pretty cool extension https://pypi.org/project/jupytext/
Re: JupyterLab 4.0
#5Anyone know about compatibility with existing notebooks? Presumably stellar, right? For now, I need jupytext (which is a great extension), so then I stay with v3.6 until jupytext is resolved. For this announcement - or in the changelog - it would be great to know why it is a major version bump - what is the major compatibility change?
I think if they made breaking changes to the notebook format, they'd mention this right away.
Re: JupyterLab 4.0
#6I see no mention of an improved debugger. IMHO, the atrocious debugger in JupyterLab is one of the primary reasons why it is difficult to write good code in this environment. Even a simple improvement like remembering the sizes of various subpanels in the debugger sidebar will make me feel like I am not pulling teeth when I use it. And don't get me started on inspecting the value of variables. If you are looking for…
Re: JupyterLab 4.0
#7I see no mention of an improved debugger. IMHO, the atrocious debugger in JupyterLab is one of the primary reasons why it is difficult to write good code in this environment. Even a simple improvement like remembering the sizes of various subpanels in the debugger sidebar will make me feel like I am not pulling teeth when I use it. And don't get me started on inspecting the value of variables. If you are looking for…
Re: JupyterLab 4.0
#8Re: JupyterLab 4.0
#9[flagged]
Re: JupyterLab 4.0
#10Anyone know about compatibility with existing notebooks? Presumably stellar, right? For now, I need jupytext (which is a great extension), so then I stay with v3.6 until jupytext is resolved. For this announcement - or in the changelog - it would be great to know why it is a major version bump - what is the major compatibility change?
This is only a change in the interface. I don't think there is any underlying change in the notebook format. Your old notebooks are completely safe. P.S. Juptext is a pretty cool extension https://pypi.org/project/jupytext/
jupytext is great, you can also review your notebooks as `.ipynb` files using GitNotebooks [https://gitnotebooks.com]. (I'm the solo dev)