-
-
Notifications
You must be signed in to change notification settings - Fork 131
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PR: Use JupyterLab to render notebooks #264
Conversation
Hello @jitseniesen! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found: There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻 Comment last updated at 2020-04-29 10:04:13 UTC |
Amazing work @jitseniesen !!! Keep it up :-) |
Pretty nice!! I just have one question: is this going to create one server instance per notebook? |
I am planning to use the same approach as currently at the start, which is one server instance per directory. However, I want to look at whether it is possible to have only one server instance which can render all notebooks regardless of where they are stored. Unless you think it's preferable to have one server instance per notebook. |
The current approach is really one server per user home directory. So if you want to open a notebook in
That probably won't work on Windows, in case users want to load notebooks from |
Ok, I won't change that in this PR, let's try to stick to one server per home dir. |
That looks pretty neat!! Thanks @jitseniesen for working on this! But what about the connection with the IPython console? Is that working? |
I tried it out and the old code still seems to work, which is a big relief. You can open a console, access the variables from the notebook in the console and in the variable explorer, and changes made in the console are reflected in the notebook. Let me know if I need to test anything else. |
Codecov Report
|
@jitseniesen, you can remove support for Python 2 in version 0.3, if you want. |
96665d4
to
cdcac3c
Compare
NB: I am not sure whether the save is performed before the function | ||
returns. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is probably not true because almost all JS operations are asynchronous.
I want to get rid of the side bar on the left with the commands and replace it with a menu bar, accessing the same commands (and more). However, I am thinking to leave that to another PR. Apart from that, I need to write some documentation while things are still fairly fresh in my mind, and then I think this is ready. |
I'm fine with that. For a future PR you should also consider to add some extra JupyterLab extensions. For instance, the ones necessary to display Bokeh or Plotly plots. |
At the moment, there is no way to specify the file name of the notebook, it is assumed to be "test.ipynb"
Fix taken from jupyterlab/jupyerlab#218397d1
Update the CSS selector for the save button. Moreover, the save is now done on mousedown, not on click.
Specify kernelspec, so that user is not asked for it.
The new notebook server under JupyterLab does not include a header anymore which needs to be hidden, so this function is no longer needed.
MathJax is not used and the URL is no longer active, generating a warning.
The prompt has a slightly different format in JupyterLab.
Otherwise tests can (and do) influence each other
Support for Python 2 will be dropped in next release.
The instructions are more complicated now that the plugin includes a notebook server written in TypeScript.
This is far from ready; I just want to show my progress.This PR updates the plugin to use the JupyterLab framework instead of the classic notebook interface, because JupyterLab is the future.
To do list:
test.ipynb
Remove sidebar? Add menubar?deferred to issue Replace sidebar by menubar in new notebook server #270Fixes #261