![Oracle Drags Its Feet in the JavaScript Trademark Dispute](https://cdn.sanity.io/images/cgdhsj6q/production/919c3b22c24f93884c548d60cbb338e819ff2435-1024x1024.webp?w=400&fit=max&auto=format)
Security News
Oracle Drags Its Feet in the JavaScript Trademark Dispute
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
jupyterlab_sage2
Advanced tools
A JupyterLab extension integrating the Jupyter data science workflow with the SAGE2 collaborative system.
A JupyterLab extension to integrate SAGE2 into the JupyterLab scientific workflow.
Three researchers using JupyterLab and SAGE2 together with the jupyterlab_sage2 extension.
The goal of this extension is to use SAGE2 with JupyterLab to integrate existing data science workflows into the collaborative software.
5.0.0
or newer to use all current JupyterLab functionality.This extension to JupyterLab allows a user to simultaneously connect to multiple SAGE2 servers and share JupyterLab content with SAGE2, including:
.ipynb
Notebook FileFrom the JupyterLab launcher, open the SAGE2 widget under "Other." Once the SAGE2 Widget is opened, a server connection can be created by clicking the green '+' button and entering the server Address. A Server Name can be specified in order to more easily refer to a server later.
The plugin displays current server connections -- these connections are persistent whether or not the widget is open. The gold Star icon allows a user to choose a 'favorite' SAGE2 server which they may send content to more often.
Two SAGE2 Connections. Left: A SAGE2 connection which is closed (server turned off, incorrect IP, firewall issue). Right: A successful SAGE2 server connection.
SAGE2 and this JupyterLab Plugin supports a variety of cell content, seen below. In order to best replicate the content in Jupyter Notebooks, SAGE2 will render:
image
, html
, and text
cell Output
Code Cells shared to SAGE2. These include
html
and image
output, an Error message, and a few enabled Code Overlays.
To select a Notebook from which to send content, simply open the notebook in JupyterLab. With a Notebook active, open the SAGE2 menu in the Menu Bar (pictured below) to choose the content to share.
Sending a Content to '★' sends the content to the Favorited server, while sending content to '...' opens a dialog in which a user may choose one of the SAGE2 connections to send to.
Notebooks are sent to SAGE2 and rendered using nbviewer. This requires that the SAGE2 server has an externally accessible IP or hostname which nbviewer can access. Notebook cells are rendered as images and automatically updated when a cell is re-run.
There are two methods of managing content shared from JupyterLab to SAGE2. First, you can simply close apps from within the SAGE2 UI and cell updates will no longer be sent. This allows you to remove content based on what you currently see on the display. This UI can be accessed by clicking on the URL displayed for a SAGE2 Connection in JupyterLab.
Alternatively, you may use the Shared Content pane within the plugin. This interface displays all Notebooks with shared content. Upon selecting a notebook, the individual cells currently shared are also displayed. You may remove a single cell at a time or all cells from the notebook. This allows you to manage content based on from where the content originated.
jupyter labextension install jupyterlab_sage2
To try JupyterLab with SAGE2, use the sage2/jupyterlab-datascience-notebook
Docker image. This image is built FROM
the jupyter/datascience-notebook
and includes Python 3, R, and Julia as well as a variety of data science packages.
docker pull sage2/jupyterlab-datascience-notebook
docker run -it --rm -p 8888:8888 sage2/jupyterlab-datascience-notebook:latest start.sh jupyter lab
The -p 8888:8888
maps the external port to the docker port: -p <external>:<internal>
. If you would like to select a different port to access Jupyterlab use -p <yourport>:8888
.
When starting the docker image, the console will give a JupyterLab url with an access token. To access JupyterLab, navigate your webpage to http://<yourhostname>:<yourport>/?token=<yourtoken>
.
For more information on the jupyter/datascience-notebook Docker image, visit: https://github.com/jupyter/docker-stacks/tree/master/datascience-notebook
Please direct any issues or bug reports to the repository's Issues.
If you would like to contribute, submit a Pull Request.
For a development install (requires npm
version 4 or later), do the following in the repository directory:
npm install
npm run build
jupyter labextension install .
To rebuild the package and the JupyterLab app:
jupyter lab build
To start development in watch
mode:
# start in parallel:
yarn watch
# and
jupyter lab --watch
FAQs
A JupyterLab extension integrating the Jupyter data science workflow with the SAGE2 collaborative system.
We found that jupyterlab_sage2 demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Oracle seeks to dismiss fraud claims in the JavaScript trademark dispute, delaying the case and avoiding questions about its right to the name.
Security News
The Linux Foundation is warning open source developers that compliance with global sanctions is mandatory, highlighting legal risks and restrictions on contributions.
Security News
Maven Central now validates Sigstore signatures, making it easier for developers to verify the provenance of Java packages.