Saravanan666/pypi-org huggingface dataset:
Package: jupyterlab-rise
jupyterlab_riseRISE: "Live" Reveal.js JupyterLab Slideshow extension.RequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab_riseFor JupyterLab 3.x, install version prior to 0.40.0:pipinstall"jupyterlab_rise<0.40.0"UninstallTo remove the extension, execute:pipuninstalljupyterlab_riseTroubleshootIf 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:jupyterlabextensionlistContributingDevelopment 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_rise directory# Install package in development modepipinstall-e".[test]"# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Server extension must be manually installed in develop modejupyterserverextensionenablejupyterlab_rise# 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 uninstall# Server extension must be manually disabled in develop modejupyterserverextensiondisablejupyterlab_rise
pipuninstalljupyterlab_riseIn 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-risewithin that folder.Testing the extensionIntegration 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 extensionSeeRELEASE
Package: jupyterlab-rklogo-extension
jupyterlab_rklogo__extension[text]To install the prebuilt extension from a wheel:Custom logos applied to:JupyterLab IDERetroLab homepageRetroLab notebooksfaviconsBuilding 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-robodyno-blockly
jupyterlab_robodyno_blocklyRobodyno JupyterLab blockly demoRequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab-robodyno-blocklyUninstallTo remove the extension, execute:pipuninstalljupyterlab-robodyno-blocklyContributingDevelopment 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_robodyno_blockly 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-robodyno-blocklyIn 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-robodyno-blocklywithin 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 extensionSeeRELEASERobodyno APIjupyter-lab-blocklya new package
Package: jupyterlab-robotmode
MarketSquare jupyterlab_robotmodeA JupyterLab extension which adds CodeMirror mode for Robot Framework syntaxPrerequisitesJupyterLabInstallationFor JupyterLab>3Note: Support for JupyterLab 4 and Notebook 7 is in the planning stage: see
discussion on#14.pipinstalljupyterlab_robotmodeorcondainstalljupyterlab_robotmode-cconda-forgeFor JupyterLab <=2Note: This will pull a significantly older, unmaintained version of the extension.jupyterlabextensioninstall@marketsquare/jupyterlab_robotmode
Package: jupyterlab-rsw
jupyterlab_rswThe jupyterlab_rsw JupyterLab plugin provides features for integrating JupyterLab with RStudio Workbench.FeaturesProvides a button on the main toolbar that will bring the user to the RStudio Workbench homepageProvides the command "Return to RStudio Workbench Home" that can be accessed through the Command Palette to bring the user to the RStudio Workbench homepage.Provides a "Proxied Servers" sidebar view that allows users to access their remote servers from RStudio Workbench environments.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_rswUninstallTo remove the extension, execute:pipuninstalljupyterlab_rsw
Package: jupyterlab-run-and-reload
jupyterlab_run_and_reloadA JupyterLab extension to run all notebook cells and reload static content (e.g. PDF).This extension is motivated by the use ofpylatexin a notebook on Jupyter Lab. When you run a notebook that creates a PDF file, you normally have to manually reload the file if it is already open. With this extension you can simply run your notebook and the PDF file gets reloaded automatically. Like this:The extension provides two commands"Run all cells and reload PDFs"."Restart kernel, run all cells and reload PDFs."This commands are available in a notebook in multiple places:Under the run menuUnder the keyboard shortcut ctrl + shift + D and ctrl + alt + shift + D respectivelyIn the command palette (ctrl + shift + C)RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_run_and_reloadUninstallTo remove the extension, execute:pipuninstalljupyterlab_run_and_reloadContributingDevelopment 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_run_and_reload 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_run_and_reloadIn 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_run_and_reloadwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-rwth
jupyterlab_rwthThe RWTH JupyterLab extension.RequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab_rwthUninstallTo remove the extension, execute:pipuninstalljupyterlab_rwthContributingDevelopment 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_rwth 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_rwthIn 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-rwthwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-scenes
jupyterlab_scenesDefine subsets of code cells as scenes and execute them.UsageThe command "Toggle Scene Cell" attaches a cell to the active scene (or removes it again). Scene membership is indicated by the purple dot at the right end of the cell.The active scene is the scene that is currently displayed (purple dots) and can be edited.All cells of a scene are executed by clicking the run button in the scene.One cell can be part of multiple scenes.By clicking theinitbutton, one scene can be chosen to be automatically executed as the kernel becomes ready (due to a restart or at the initial loading of the notebook).If a notebook with an already running kernel is opened, the init scene isnotexecuted.Only one scene can be an init scene.To run a scene namedMy Favourite Sceneprogramatically, dofrom ipylab import JupyterFrontEnd
JupyterFrontEnd().commands.execute('scenes:run-scene', 'My Favourite Scene')But you may run only one scene at a time. No excessive looping as the scenes are executed only after the cell that launches therun-scenecommand is finished.RequirementsJupyterLab >= 4.0InstallTo install the extension, execute:pipinstalljupyterlab_scenesUninstallTo remove the extension, execute:pipuninstalljupyterlab_scenesPackaging the extensionSeeRELEASE
Package: jupyterlab-scheduler
jupyterlab_schedulerA simple plugin for scheduling files for recurring execution using the cron utility within the Jupyter Lab UI. Use casesSecurity Note: Cron jobs are executed under the permission set of the JupyerLab process; if you start jupyter as root (not recommended!) every job that is scheduled via the UI will also run as root.ScreenshotsScheduling a jobViewing Scheduled JobsViewing Run LogsPrerequisitesJupyterLabCron installed on the JupyterLab hostInstallationTo install using pip:pipinstalljupyterlab_scheduler

jupyterlabextensioninstalljupyterlab_schedulerDevelopmentFor a development install (requires npm version 4 or later), do the following in the repository directory:# Clone the repo to your local environment# Move to jupyterlab_scheduler directory# Install dependenciesnpminstall# Install your development version of the extensionjupyterlabextensioninstall.You run JupyterLab in watch mode to watch for changes in the extension's source and automatically rebuild.# Run jupyterlab in watch mode & compile JS on changenpmrunwatch&jupyterlab--watchNow every change will be built locally and bundled into JupyterLab. Be sure to refresh your browser page after saving file changes to reload the extension (note: you'll need to wait for webpack to finish, which can take 10s+ at times).# Run jupyterlab in auto reload mode & compile JS on changenpmrunwatch&jupyterlab--autoreload--NotebookApp.token=''--NotebookApp.password=''--no-browserWorks better when developing server extensionsNote: Make sure to close any old npm run watch jobs that may be running in the background.PublishingUpdate version number in:package.jsonjupyterlab_scheduler/_version.pyUpdate JavaScript files:npminstallBuild the server-side portion of the plugin for disitibution on Pypi:python3setup.pysdistbdist_wheel

python3-mtwineupload--repositorypypidist/*Uninstalljupyterlabextensionuninstalljupyterlab_scheduler
Package: jupyterlab-scicap-ui
jupyterlab-scicap-uiThis package is a jupyterlab extension for the Science Capsule user interface.
It loads thescicap-uiReact app into a widget that can be launched from the jupyterlab launcher window.Installjlpm
jlpmbuild
jupyterlabextensioninstall.# 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--watchBuild and PublishFirst commit changes and upgrade the package version using npm.npm version patchThen build the labextension and python distribution.jlpm run build:distThen publish the.whlfile to pypi.jlpm run publishIn order to publish, you will have to authenticate with pypi and your account must have permission to administer thejupyterlab-scicap-ui packageon pypi.
Package: jupyterlab-scicap-verdant
Jupyterlab Scicap VerdantThis project is an adaptation of the Verdant project for Science Capsule. Events from Verdant are intercepted and sent to an API so that jupyter events can be stored with other Science Capsule events.Verdant🌱🌿🌱 Verdant is a JupyterLab extension that automatically records history of all experiments you run in a Jupyter notebook, and stores them in a tidy .ipyhistory JSON file designed to be work alongside and compliment any other version control you use, like SVN or Git. Verdant also visualizes history of individual cells, code snippets, markdown, and outputs for you, for quick checks and references as you work.For design discussion and the research behind this check out thepaper:Mary Beth Kery, Bonnie E. John, Patrick O’Flaherty, Amber Horvath, and
Brad A. Myers. 2019. Towards Effective Foraging by Data Scientists to Find
Past Analysis Choices. In Proceedings of ACM SIGCHI, Glasgow, UK, May
2019 (CHI’19), 11 pages. DOI: 10.475/123 4Install for Local DevelopmentIf developing and making changes to the package locally, run the following commands after making changes:# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Enable the server extensionjupyterserverextensionenablejupyterlab_scicap_verdant# Rebuild extension Typescript source after making changesjlpmrunbuildCheck that the extension is installed and enabled:jupyterlabextensionlistRun jupyterlab:jupyterlabBuild and PublishFirst rebuild the labextension and commit changes.jlpm run build
pip install -e .
git commit add .
git commit -m "My updates"Then upgrade the package version using npm.npm version patchThen build the python distribution.jlpm run build:distThen publish the.whlfile to pypi.jlpm run publishIn order to publish, you will have to authenticate with pypi and your account must have permission to administer thejupyterlab-scicap-verdant packageon pypi.AcknowledgementsThe original Verdant library was authored by Mary Beth Kery. Research has been funded by Bloomberg L.P. and has been conducted at the Bloomberg L.P. and at theNatural Programming Groupat theHuman-Computer Interaction Instituteat Carnegie Mellon University. Thank you to theJupyterLab projectand also to all our awesome study participants for volunteering early design feedback!
Package: jupyterlab-server
jupyterlab serverMotivationJupyterLab Server sits between JupyterLab and Jupyter Server, and provides a
set of REST API handlers and utilities that are used by JupyterLab. It is a separate project in order to
accommodate creating JupyterLab-like applications from a more limited scope.Installpip install jupyterlab_serverTo include optionalopenapidependencies, use:pip install jupyterlab_server[openapi]To include optionalpytest_plugindependencies, use:pip install jupyterlab_server[test]UsageSee the full documentation forAPI docsandREST endpoint descriptions.Extending the ApplicationSubclass theLabServerAppand provide additional traits and handlers as appropriate for your application.ContributionPlease seeCONTRIBUTING.mdfor details.
Package: jupyterlab-simpledark
jupyterlab SimpledarkA (growing) dark theme collection for JupyterLab.PreviewsSimpledark OriginalSimpledark FreshRequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-simpledarkContributingDevelopment 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-simpledark 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-simpledarkIn 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-simpledarkwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-skip-traceback
jupyterlab-skip-tracebackA JupyterLab extension for rendering Errors with a copy/paste button and expand/collapse.This is inspired by the notebook versionhere.RequirementsJupyterLab >= 4.0Installpipinstalljupyterlab-skip-tracebackContributingDevelopment 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-skip-traceback directory# Install package in development modepipinstall-e.# Link your development version of the extension with JupyterLabjupyter-labextensiondevelop.--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=FalsePublishingBefore starting, you'll need to have run:pip install twine jupyter_packagingUpdate the version inpackage.jsonand update the release date inCHANGELOG.mdCommit the change in step 1, tag it, then push itgit commit -am <msg>
git tag vX.Z.Y
git push && git push --tagsCreate the artifactsrm -rf dist tsconfig.tsbuildinfo lib jupyterlab-skip-traceback/labextension jupyterlab_skip_traceback-*.tar.gz jupyterlab_skip_traceback-*.whl
hatch build .Test this against the test pypi. You can then install from here to test as well:gitwine upload --repository-url https://test.pypi.org/legacy/ jupyterlab_skip_traceback-*.tar.gz jupyterlab_skip_traceback-*.whl
# In a new venv
pip install --index-url https://test.pypi.org/simple/ jupyterlab_skip_tracebackUpload this to pypi:twine upload jupyterlab_skip_traceback-*.tar.gz jupyterlab_skip_traceback-*.whlUninstallpipuninstalljupyterlab-skip-tracebackHistoryThis plugin was contributed back to the community by theD. E. Shaw group.LicenseThis project is released under aBSD-3-Clause license.We love contributions! Before you can contribute, please sign and submit thisContributor License Agreement (CLA).
This CLA is in place to protect all users of this project."Jupyter" is a trademark of the NumFOCUS foundation, of which Project Jupyter is a part.