Live data from Hacker News

JupyterLab 4.0

blog.jupyter.org

1–10 of 199 posts

Re: JupyterLab 4.0

#2
Anyone 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?

Re: JupyterLab 4.0

#3
I 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 more than an object within an object, you might as well go back to print statements.

Re: JupyterLab 4.0

#4
post #2

Anyone 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/

Re: JupyterLab 4.0

#5
post #2

Anyone 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 would think of JupyterLab as more of an IDE, and the major version bump need not affect their notebook format.

I think if they made breaking changes to the notebook format, they'd mention this right away.

Re: JupyterLab 4.0

#6

I 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…

Also it has a poor multi-user experience.

Re: JupyterLab 4.0

#7

I 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…

Do you know how it compares to using Visual Studio Code's debugger with notebooks? I'm wanting to find a notebook debugger recommendation for my students.

Re: JupyterLab 4.0

#10
post #2

Anyone 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/

nbformat is reference implementation of the notebook format: https://github.com/jupyter/nbformat No recent major releases.

jupytext is great, you can also review your notebooks as `.ipynb` files using GitNotebooks [https://gitnotebooks.com]. (I'm the solo dev)

Post reply on HN