On behalf of Azure Notebooks team, a huge congrats to the team!
If you like to try it, pick any of your libraries, right click and select “open in JupyterLab”.
JupyterLab is ready for users
121–130 of 250 posts
Re: JupyterLab is ready for users
#122So let's say I am progressing inside a jupyter notebook top to bottom. I run code blocks, then some markdown, then code blocks, and so on. At some point I need to drop down to the terminal to run something. I run commands in the terminal I collect some results or collect some info and go back to my notebook to resume my work inside it. Later I need to look up something in a text file. I open a certain text file. Brow…
Jupyter doesn’t track the execution history of your cells like this.
However, you can run the shell commands straight from a notebook cell (use the %%bash cell magic or prepend the line with !).
Not sure what to do about editing data files. If you can do this with something like awk, just use a shell magic cell, but if it needs to be done manually I guess you’re stuck manually documenting this in markdown?
Re: JupyterLab is ready for users
#123I very heavily rely on the "official" notebook extensions from https://github.com/ipython-contrib/jupyter_contrib_nbextensi...
This especially includes things like "Table of Contents", "Variable Inspector", "Ruler", and "Execute Time". How easy will it be to have all of this functionality in the JupyterLab notebooks? There's certainly advantages to having data/terminals/notebooks in an IDE-style layout, but for the moment it would still be two steps back, one step forward for me personally. This is to disparage the effort, JupyterLab clearly is the future!
Re: JupyterLab is ready for users
#124Is there a way to integrate a debugger and browse variables? I have been using Spyder for casual programming, and don’t think I could do without a debugger.
For the classic notebook, there's a "Variable Inspector" plugin that's quite neat. See https://github.com/ipython-contrib/jupyter_contrib_nbextensi...
I'm hoping these extensions will be available in JupyterLab as well
Re: JupyterLab is ready for users
#125At the same time, the community has faced challenges in using various software workflows with the notebook alone, such as running code from text files interactively. The classic Jupyter Notebook, built on web technologies from 2011, is also difficult to customize and extend. Do I read this correctly as hinting that Jupyter Notebook is being replaced by an IDE?
Having used JupyterLab alpha extensively, I don't think so. JupyterLab makes the 'notebook' one type of document, rather than the only type of document.
So it extends Jupyter Notebooks by giving you new IDE-like features, whilst retaining the ability to write notebooks.
Re: JupyterLab is ready for users
#126I very heavily rely on the "official" notebook extensions from https://github.com/ipython-contrib/jupyter_contrib_nbextensi... This especially includes things like "Table of Contents", "Variable Inspector", "Ruler", and "Execute Time". How easy will it be to have all of this functionality in the JupyterLab notebooks? There's certainly advantages to having data/terminals/notebooks in an IDE-style layout, but for the m…
First of all these are not "official" (hence why it's a different organisation on GitHub) and all is maintained by community.
It will take some time to port all the existing extensions, but the good news is that JupyterLab has been thought to work with extensions (actually everything in JupyterLab is an extension with no privileged component), so it will be easier to write these for JupyterLab than for current notebook.
The documentation on writing extension is also way better than for Classic notebook, and we had new contributor writing extension in 2 to 3 hours.
So we encourage you to try and send us feedback !
Re: JupyterLab is ready for users
#127Is it clear yet how one will use text editors (emacs, vim) with JupyterLab?
Re: JupyterLab is ready for users
#128On behalf of Azure Notebooks team, a huge congrats to the team! If you like to try it, pick any of your libraries, right click and select “open in JupyterLab”.
Much love from the Jupyter Team to the Azure Notebook team !
Re: JupyterLab is ready for users
#129is there now a viable way to create multi-user read-only notebooks ?
so that a data scientist can prototype a dashboard on jupyter and then multiple people can use the dashboard ?
Re: JupyterLab is ready for users
#130At the same time, the community has faced challenges in using various software workflows with the notebook alone, such as running code from text files interactively. The classic Jupyter Notebook, built on web technologies from 2011, is also difficult to customize and extend. Do I read this correctly as hinting that Jupyter Notebook is being replaced by an IDE?
We should disambiguate the term "jupyter notebook" here. Jupyter notebooks, as documents that contain code, markdown, math, widgets, etc., are a central feature of JupyterLab. Jupyter notebooks are not going away, and are getting better in JupyterLab.
The "Jupyter Notebook" web application (i.e., the browser application that was originally released in 2011) will eventually be replaced with JupyterLab.