Personal tools
Skip to content. | Skip to navigation
This package contains a Jupyter kernel for Singular, to enable using Jupyter as the front end for Singular.
jupyter_kernel_test is a tool for testing Jupyter kernels. It tests kernels for successful code execution and conformance with the Jupyter Messaging Protocol (currently 5.0). Install Install it with pip (python3.4 or greater required): pip3 install jupyter_kernel_test Usage To use it, you need to write a (python) unittest file containing code samples in the relevant language which test various parts of the messaging protocol. A short example is given below, and you can also refer to the test_ipykernel.py and test_irkernel.py files for complete examples. Some parts of the messaging protocol are relevant only to the browser-based notebook (rich display) or console interfaces (code completeness, history searching). Only parts of the spec for which you provide code samples are tested. Run this file directly using python, or use nosetests or py.test to find and run it. Example import unittest import jupyter_kernel_test class MyKernelTests(jupyter_kernel_test.KernelTests):
jupyter-lspMulti-[Language Server][language-server] WebSocket proxy for your Jupyter notebook or lab server. For Python 3.6+.> See the parent of this repository, > [jupyterlab-lsp]( for the > reference client implementation for [JupyterLab][]. Language Serversjupyter-lsp does not come with any Language Servers! Learn more about installing and configuring [language servers][language servers...
Jupyter Packaging Tools to help build and install Jupyter Python packages that require a pre-build step that may include JavaScript build steps. Install pip install jupyter-packaging Usage There are three ways to use jupyter-packaging in another package. In general, you should not depend on jupyter_packaging as a runtime dependency, only as a build dependency. As a Build Requirement Use a pyproject.toml file as outlined in pep-518. An example: [build-system] requires = ["jupyter_packaging>=0.10,<2"] build-backend = "setuptools.build_meta" Below is an example setup.py using the above config. It assumes the rest of your metadata is in setup.cfg. We wrap the import in a try/catch to allow the file to be run without jupyter_packaging so that python setup.py can be run directly when not building. from setuptools import setup try: from jupyter_packaging import wrap_installers, npm_builder builder = npm_builder() cmdclass = wrap_installers(pre_develop=builder, pre_dist=builder)