Saravanan666/pypi-org huggingface dataset:
Package: jupyterlab-ou-brand-extension
jupyterlab_ou_brand_extensionSimple extension to apply custom brand logos JupyterLab.DemoJupyterLab site via JupyterLiteDemoRetroLab / notebook v.7 site via JupyterLiteTo install the prebuilt extension from a wheel:pip3 install --upgrade https://raw.githubusercontent.com/innovationOUtside/jupyterlab_ou_brand_extension/main/dist/jupyterlab_ou_brand_extension-0.1.0-py3-none-any.whlCustom logos applied to:JupyterLab IDERetroLab homepageRetroLab notebooksfaviconsAbout:Custom Branded Logos for JupyterLab and RetroLab (Jupyter notebook v.7)Building and Pushing Newly Built Wheels to PyPi# Buildpipinstallbuild#Install the packagepipinstall.# Node MUST BE INSTALLEDpython-mbuild# packages built into ./dist# Push to PyPipipinstalltwine
twineuploadMY_PACKAGE.whl
Package: jupyterlab-pachyderm-theme
JupyterLab Pachyderm ThemeA JupyterLab Pachyderm theme with a splash extension.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_pachyderm_themeUninstallTo remove the extension, execute:pipuninstalljupyterlab_pachyderm_themeContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_pachyderm_theme directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_pachyderm_themeIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink named@pachyderm/jupyterlab-pachyderm-themewithin that folder.
Package: jupyterlab-pausable-contextual-help
jupyterlab_pausable_contextual_helpCustomized Jupyterlab Contextual Help Panel That Allows Manually Update When Press F1.Auto update can still be enabled in the context menu.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_pausable_contextual_helpUninstallTo remove the extension, execute:pipuninstalljupyterlab_pausable_contextual_helpContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_pausable_contextual_help directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_pausable_contextual_helpIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab_pausable_contextual_helpwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-pioneer-custom-event-demo
JupyterLab Pioneer Custom Event DemoA JupyterLab extension that generates telemetry data when a user clicks a specific button.This extension is an example of how to write a simple extension that leverages functionalities provided byjupyterlab-pioneerto generate telemetry data for custom events.Get startedRequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-pioneer-custom-event-demoTroubleshootIf you are seeing the frontend extension, but it is not working, check
that the server extension is enabled:jupyterserverextensionlistIf the server extension is installed and enabled, but you are not seeing
the frontend extension, check the frontend extension is installed:jupyterlabextensionlistHow to implement a custom event extensionhttps://github.com/educational-technology-collective/jupyterlab-pioneer-custom-event-demo/blob/main/doc/how-to-implement-a-custom-event-extension.md
Package: jupyterlab-play-cell-button
jupyterlab_play_cell_buttonAdds a play button to cells in jupyterlabRequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_play_cell_buttonUninstallTo remove the extension, execute:pipuninstalljupyterlab_play_cell_buttonContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_play_cell_button directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_play_cell_buttonIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink named@epi2melabs/jupyterlab-play-cell-buttonwithin that folder.
Package: jupyterlab-plugin-graph
jupyterlab-plugin-graphJupyterLab extension to show an interactive dependency graph of all the installed plugins.RequirementsJupyterLab >= 2.0Installpipinstalljupyterlab-plugin-graphContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-plugin-graph directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseUninstallpipuninstalljupyterlab-plugin-graph
Package: jupyterlab-powerpoint
jupyterlab_powerpointCreating PowerPoints from jupyter notebooksInstallpipinstalljupyterlab_powerpoint
jupyterlabextensioninstalljupyterlab_powerpoint
jupyterserverextensionenable--pyjupyterlab_powerpointWorkflowGenerate a notebook from a prexisting notebook (includes metadata necessary to reconstruct the original powerpoint)Parameterize notebook, modify parts/text/datahook in toPapermill, leverage python, rexecute daily, etcGenerate a powerpoint from the notebook
Package: jupyterlab-primehub
jupyterlab-primehubJupyterlab extension for PrimeHubRequirementsJupyterLab >= 2.2.5Installjupyterlabextensioninstall@infuseai/jupyterlab-primehub
pipinstalljupyterlab_primehub
jupyterserverextensionenablejupyterlab_primehubUninstalljupyterlabextensionuninstall@infuseai/jupyterlab-primehub
jupyterserverextensiondisablejupyterlab_primehub
pipuninstalljupyterlab_primehubBuild the Docker ImageExample docker file:FROMjupyter/base-notebookARGPRIMEHUB_EXTENSION_VERSION="0.1.4"USER$NB_UIDRUNpipinstall--no-cache-dirjupyterlab_primehub~=$PRIMEHUB_EXTENSION_VERSION&&\jupyterserverextensionenablejupyterlab_primehub&&\jupyterlabextensioninstall@infuseai/jupyterlab-primehub@~v$PRIMEHUB_EXTENSION_VERSION&&\jupyter-labbuildTroubleshootingIf the JupyterLab < 2.2.5, you may see this error:ValueError: No version of @infuseai/jupyterlab-primehub could be found that is compatible with the current version of JupyterLab. However, it seems to support a new version of JupyterLab. Consider upgrading JupyterLab.

Conflicting Dependencies:
JupyterLab              Extension      Package
>=2.1.2 <2.2.0          >=2.2.5 <3.0.0 @jupyterlab/application
>=2.1.1 <2.2.0          >=2.2.5 <3.0.0 @jupyterlab/apputils
>=2.1.2 <2.2.0          >=2.2.5 <3.0.0 @jupyterlab/notebook
>=5.1.0 <5.2.0          >=5.2.4 <6.0.0 @jupyterlab/servicesIf thejupyter-clientversion is too old, you may see this error:fromjupyter_clientimportAsyncKernelManagerImportError:cannotimportname‘AsyncKernelManager’If theipykernelversion is too old, you may see this error:AttributeError:'AsyncKernelManager'objecthasnoattribute‘cleanup_resources'ContributingPlease checkDEVELOPMENT.
Package: jupyterlab-prolog-codemirror-extension
JupyterLab Prolog CodeMirror ExtensionA JupyterLab extension providing a Prolog CodeMirror mode based onextension-cookiecutter-ts.Also see theJupyter kernel for Prolog.RequirementsJupyterLab >= 3.1InstallTo install the extension, execute:pipinstalljupyterlab_prolog_codemirror_extensionUninstallTo remove the extension, execute:pipuninstalljupyterlab_prolog_codemirror_extensionContributingDevelopment installNotes:You will need NodeJS to build the extension package.A TypeScript version < 4.4.0 is required. It can be installed withnpm install typescript@4.1.3Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_prolog_codemirror_extension directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_prolog_codemirror_extensionIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab_prolog_codemirror_extensionwithin that folder.Upload to PyPIThis extension is available as a Python package on thePython Package Index. A new version of the package can be published in the following way:Install the requirements build and twine:pip install build twineIncrease the version inpackage.jsonCreate the distribution files:python -m buildUpload the package to PyPI:twine upload dist/*For further information, see thePackaging Python Projects Tutorial.
Package: jupyterlab-promptclose
jupyterlab-promptclosePrompt when JupyterLab window is closed.Do you find yourself using theCtrl-wkeyboard shortcut (delete the previous word in Bash) in a JupyterLab terminal and accidentally closing your browser window instead? Then install this extension and you should see a prompt before the window is closed.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab-promptcloseUninstallTo remove the extension, execute:pipuninstalljupyterlab-promptcloseContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab-promptclose directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmrunbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmrunwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm run buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab-promptcloseIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab-promptclosewithin that folder.
Package: jupyterlab-proxy-gui
jupyterlab-proxy-guiA JupyterLab extension show endpoins of proxy routes as new tabs. JupyterHub and the configurable-http-proxy is used to forward the data.A docker setup can be found atexamples/dockerThis extension is composed of a Python package namedjupyterlab_proxy_guifor the server extension and a NPM package namedjupyterlab-proxy-guifor the frontend extension.RequirementsJupyterLab >= 3.0JupyterHubInstallNote: You will need NodeJS to install the extension.pipinstalljupyterlab_proxy_gui
jupyterlabbuildTroubleshootIf you are seeing the frontend extension but it is not working, check
that the server extension is enabled:jupyterserverextensionlistIf the server extension is installed and enabled but you are not seeing
the frontend, check the frontend is installed:jupyterlabextensionlistIf it is installed, try:jupyterlabclean
jupyterlabbuildContributingInstallThejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Move to jupyterlab-proxy-gui directory# Install server extensionpipinstall-e.# Register server extensionjupyterserverextensionenable--pyjupyterlab_proxy_gui--sys-prefix# Install dependenciesjlpm# Build Typescript sourcejlpmbuild# Link your development version of the extension with JupyterLabjupyterlabextensionlink.# Rebuild Typescript source after making changesjlpmbuild# Rebuild JupyterLab after making any changesjupyterlabbuildYou can watch the source directory and run JupyterLab in watch mode to watch for changes in the extension's source and automatically rebuild the extension and application.# Watch the source directory in another terminal tabjlpmwatch# Run jupyterlab in watch mode in one terminal tabjupyterlab--watchUninstallpipuninstalljupyterlab_proxy_gui
jupyterlabextensionuninstalljupyterlab-proxy-gui
Package: jupyterlab-pullrequests
jupyterlab-pullrequestsA JupyterLab extension for reviewing pull requests.For now, it supports GitHub and GitLab providers.PrerequisitesJupyterLab 3.xfor JupyterLab 2.x, see the2.xbranchjupyterlab-git>=0.30.0For GitLab, you will need alsodiff-match-patchUsageOpen the pull request extension from the tab on the left panelInstallation1. Install the extension with the following stepsWith pip:pipinstalljupyterlab-pullrequestsOr with conda:condainstall-cconda-forgejupyterlab-pullrequestsFor GitLab, in addition, you will need topipinstalldiff-match-patchOr with conda:condainstall-cconda-forgediff-match-patch2. Getting your access tokenFor GitHub, the documentation isthere. The token scope must berepo.For GitLab, the documentation isthere. The token scope must beapi.Remember that this token is effectively a password for your account.Do notshare it online or check the token into version control,
as people can use it to access all of your data.3. Setting your access token in JupyterLab Pull RequestsYou now need to add the credentials you got from the provider
to your server configuration file. Instructions for generating a configuration
file can be foundhere.
Once you have identified this file, add the following lines to it:c.PRConfig.access_token='<YOUR_ACCESS_TOKEN>'where "<YOUR_ACCESS_TOKEN>" is the string value you obtained above.If you are using GitLab instead of GitHub, you also need to set the
provider:c.PRConfig.provider='gitlab'Congrats, you did it! Launch JupyterLab and look for the Pull Request tab on the left! 🎉If you are not using GitHub.com or GitLab.com, you can set the API base URL of your provider
with the configurable parameterPRConfig.api_base_url.SettingsThis extension asserver settings.PRConfig.access_token: Access token to be authenticated by the providerPRConfig.provider:github(default) orgitlabPRConfig.api_base_url: Provider API base url (default tohttps://api.github.comexcept if provider isgitlabthen it defaults tohttps://gitlab.com/api/v4/)TroubleshootingIf you are seeing the following error[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chainand the certificates are installed on your machine, you will need to set theSSL_CERT_FILEenvironment variable to point to your system certificates bundle. For example:export SSL_CERT_FILE=/etc/ssl/certs/ca-certificates.crtDevelopmentContributingIf you would like to contribute to the project, please read ourcontributor documentation.JupyterLab follows the officialJupyter Code of Conduct.
Package: jupyterlab-purple-wave-theme
JupyterLab Horizon ThemeVSCode Horizon Theme port for JupyterLabRequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab-horizon-themeUninstallTo remove the extension, execute:pipuninstalljupyterlab-horizon-themeContributingDevelopment installNote: You will need NodeJS to build the extension package.Thejlpmcommand is JupyterLab's pinned version ofyarnthat is installed with JupyterLab. You may useyarnornpmin lieu ofjlpmbelow.# Clone the repo to your local environment# Change directory to the jupyterlab_horizon_theme directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Rebuild extension Typescript source after making changesjlpmbuildYou can watch the source directory and run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.# Watch the source directory in one terminal, automatically rebuilding when neededjlpmwatch# Run JupyterLab in another terminaljupyterlabWith the watch command running, every saved change will immediately be built locally and available in your running JupyterLab. Refresh JupyterLab to load the change in your browser (you may need to wait several seconds for the extension to be rebuilt).By default, thejlpm buildcommand generates the source maps for this extension to make it easier to debug using the browser dev tools. To also generate source maps for the JupyterLab core extensions, you can run the following command:jupyterlabbuild--minimize=FalseDevelopment uninstallpipuninstalljupyterlab_horizon_themeIn development mode, you will also need to remove the symlink created byjupyter labextension developcommand. To find its location, you can runjupyter labextension listto figure out where thelabextensionsfolder is located. Then you can remove the symlink namedjupyterlab-horizon-themewithin that folder.Testing the extensionFrontend testsThis extension is usingJestfor JavaScript code testing.To execute them, execute:jlpm
jlpmtestIntegration testsThis extension usesPlaywrightfor the integration tests (aka user level tests).
More precisely, the JupyterLab helperGalatais used to handle testing the extension in JupyterLab.More information are provided within theui-testsREADME.Packaging the extensionSeeRELEASECreditThanks toHorizon Theme for VSCodefor the great color scheme.And thanks toJupyter Atom Dark Themefor CSS elements styling.