How to Install and Uninstall python310-nbclassic Package on openSuSE Tumbleweed
Last updated: November 08,2024
1. Install "python310-nbclassic" package
This is a short guide on how to install python310-nbclassic on openSuSE Tumbleweed
$
sudo zypper refresh
Copied
$
sudo zypper install
python310-nbclassic
Copied
2. Uninstall "python310-nbclassic" package
Please follow the steps below to uninstall python310-nbclassic on openSuSE Tumbleweed:
$
sudo zypper remove
python310-nbclassic
Copied
3. Information about the python310-nbclassic package on openSuSE Tumbleweed
Information for package python310-nbclassic:
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-nbclassic
Version : 1.0.0-3.1
Arch : noarch
Vendor : openSUSE
Installed Size : 36.6 MiB
Installed : No
Status : not installed
Source package : python-nbclassic-1.0.0-3.1.src
Upstream URL : https://github.com/jupyterlab/nbclassic
Summary : Jupyter Notebook as a Jupyter Server Extension
Description :
NBClassic runs the Jupyter Notebook frontend on the Jupyter Server backend.
This project prepares for a future where JupyterLab and other frontends switch
to Jupyter Server for their Python Web application backend. Using this package,
users can launch Jupyter Notebook, JupyterLab and other frontends side-by-side
on top of the new Python server backend.
--------------------------------------------
Repository : openSUSE-Tumbleweed-Oss
Name : python310-nbclassic
Version : 1.0.0-3.1
Arch : noarch
Vendor : openSUSE
Installed Size : 36.6 MiB
Installed : No
Status : not installed
Source package : python-nbclassic-1.0.0-3.1.src
Upstream URL : https://github.com/jupyterlab/nbclassic
Summary : Jupyter Notebook as a Jupyter Server Extension
Description :
NBClassic runs the Jupyter Notebook frontend on the Jupyter Server backend.
This project prepares for a future where JupyterLab and other frontends switch
to Jupyter Server for their Python Web application backend. Using this package,
users can launch Jupyter Notebook, JupyterLab and other frontends side-by-side
on top of the new Python server backend.