experimental/cuda-ubi9/: jupyter-events-0.10.0 metadata and description

Simple index

Jupyter Event System library

author_email Jupyter Development Team <jupyter@googlegroups.com>
  • Intended Audience :: Developers
  • Intended Audience :: Science/Research
  • Intended Audience :: System Administrators
  • License :: OSI Approved :: BSD License
  • Programming Language :: Python
  • Programming Language :: Python :: 3
description_content_type text/markdown
keywords Jupyter,JupyterLab
license BSD 3-Clause License Copyright (c) 2022-, Jupyter Development Team All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
  • Homepage, http://jupyter.org
  • documentation, https://jupyter-events.readthedocs.io/
  • repository, https://github.com/jupyter/jupyter_events.git
  • changelog, https://github.com/jupyter/jupyter_events/blob/main/CHANGELOG.md
provides_extras test
  • jsonschema[format-nongpl]>=4.18.0
  • python-json-logger>=2.0.4
  • pyyaml>=5.3
  • referencing
  • rfc3339-validator
  • rfc3986-validator>=0.1.1
  • traitlets>=5.3
  • click; extra == 'cli'
  • rich; extra == 'cli'
  • jupyterlite-sphinx; extra == 'docs'
  • myst-parser; extra == 'docs'
  • pydata-sphinx-theme; extra == 'docs'
  • sphinxcontrib-spelling; extra == 'docs'
  • click; extra == 'test'
  • pre-commit; extra == 'test'
  • pytest-asyncio>=0.19.0; extra == 'test'
  • pytest-console-scripts; extra == 'test'
  • pytest>=7.0; extra == 'test'
  • rich; extra == 'test'
requires_python >=3.8
File Tox results History
18 KB
Python Wheel

Jupyter Events

Build Status Documentation Status

An event system for Jupyter Applications and extensions.

Jupyter Events enables Jupyter Python Applications (e.g. Jupyter Server, JupyterLab Server, JupyterHub, etc.) to emit events—structured data describing things happening inside the application. Other software (e.g. client applications like JupyterLab) can listen and respond to these events.


Install Jupyter Events directly from PyPI:

pip install jupyter_events

or conda-forge:

conda install -c conda-forge jupyter_events


Documentation is available at jupyter-events.readthedocs.io.

About the Jupyter Development Team

The Jupyter Development Team is the set of all contributors to the Jupyter project. This includes all of the Jupyter subprojects.

The core team that coordinates development on GitHub can be found here: https://github.com/jupyter/.

Our Copyright Policy

Jupyter uses a shared copyright model. Each contributor maintains copyright over their contributions to Jupyter. But, it is important to note that these contributions are typically only changes to the repositories. Thus, the Jupyter source code, in its entirety is not the copyright of any single person or institution. Instead, it is the collective copyright of the entire Jupyter Development Team. If individual contributors want to maintain a record of what changes/contributions they have specific copyright on, they should indicate their copyright in the commit message of the change, when they commit the change to one of the Jupyter repositories.

With this in mind, the following banner should be used in any source code file to indicate the copyright and license terms:

# Copyright (c) Jupyter Development Team.
# Distributed under the terms of the Modified BSD License.