Saravanan666/pypi-org huggingface dataset:
Package: jupyterlab-pyflyby
@deshaw/jupyterlab_pyflybyA labextension to integrate pyflyby with notebooksPyflybyhelps you get rid of the tedious task of recalling and adding import statements. This labextension takes it further by adding the import statements automatically in your notebook. For eg. executingnp.arange(10)You can decide cell where imports should be added by adding 'pyflyby-cell' cell tag to it.RequirementsJupyterLab >= 4.0Installpipinstalljupyterlab_pyflybyContributingDevelopment 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_pyflyby 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 terminaljupyter-labWith 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_pyflyby/labextension jupyterlab_pyflyby-*.tar.gz jupyterlab_pyflyby-*.whl
hatch build .Test this against the test pypi. You can then install from here to test as well:twine upload --repository-url https://test.pypi.org/legacy/ jupyterlab_pyflyby-*.tar.gz jupyterlab_pyflyby-*.whl# In a new venv
pip install --index-url https://test.pypi.org/simple/ jupyterlab_pyflybyUpload this to pypi:twine upload jupyterlab_pyflyby-*.tar.gz jupyterlab_pyflyby-*.whlUninstallpipuninstalljupyterlab_pyflybyHistoryThis 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.
Package: jupyterlab-pygments
JupyterLab Pygments ThemeThis package contains a syntax coloring theme forpygmentsmaking use of
the JupyterLab CSS variables.The goal is to enable the use of JupyterLab's themes with pygments-generated HTML.ScreencastIn the following screencast, we demonstrate how Pygments-highlighted code can make use of the JupyterLab theme.Installationjupyterlab_pygmentscan be installed with the conda package managerconda install -c conda-forge jupyterlab_pygmentsor from pypipip install jupyterlab_pygmentsDependenciesjupyterlab_pygmentsrequirespygmentsversion2.4.1.The CSS variables used by the theme correspond to the CodeMirror syntex coloring
theme defined in the NPM package@jupyterlab/codemirror. Supported versions for@jupyterlab/codemirror's CSS include0.19.1,^1.0, and,^2.0.LimitationsPygments-generated HTML and CSS classes are not granular enough to reproduce
all of the details of codemirror (the JavaScript text editor used by JupyterLab).This includes the ability to differentiate properties from general names.Licensejupyterlab_pygmentsuses a shared copyright model that enables all contributors to maintain the
copyright on their contributions. All code is licensed under the terms of the revisedBSD license.
Package: jupyterlab-python-file
jupyterlab-python-fileCreate Python Files from JupyterLabPrerequisitesJupyterLab 1.0+InstallationFor JupyterLab 3.x, the extension can be installed withpip:pipinstalljupyterlab-python-fileOr withconda:condainstall-cconda-forgejupyterlab-python-file# or with mambamambainstalljupyterlab-python-fileFor JupyterLab 1.x and 2.x:jupyterlabextensioninstalljupyterlab-python-fileDevelopmentNote: 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-python-file directory# create a new environmentcondacreate-njupyterlab-python-file-cconda-forgepythonnodejs-y
condaactivatejupyterlab-python-file# install the JupyterLab pre-releasepython-mpipinstall--prejupyterlab# 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).
Package: jupyterlab-pytutor
jupyterlab-pytutorA JupyterLab extension for pythontutor.com.
This integrates pytutor for python kernels st. the python code can be inspected by pytutorRequirementsJupyterLab >= 3.0InstallTo install the extension, execute:pipinstalljupyterlab-pytutorUninstallTo remove the extension, execute:pipuninstalljupyterlab-pytutorContributingDevelopment 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-pytutor 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-pytutorIn 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-pytutorwithin that folder.
Package: jupyterlab-quarto
JupyterLab Quarto ExtensionQuartois an open source project that combines Jupyter notebooks with flexible options to use a single source document to produce high-quality articles, reports, presentations, websites, and books in HTML, PDF, MS Word, ePub, and more. Quarto supports a wide variety of useful new features useful in technical documents, including support for LaTeX equations, citations, cross-references, figure panels, callouts, advanced page layout, and more.The JupyterLab Quarto extension allows JupyterLab to render notebooks which include Quarto markdown content.BinderYou can try an example of the extension in a notebook (though you can't actually render the notebook using Quarto) on Binder.StatusRequirementsJupyterLab >= 4.0.0InstallTo install the extension, execute:pipinstalljupyterlab-quartoUninstallTo remove the extension, execute:pipuninstalljupyterlab-quartoContributingDevelopment 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-quarto 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-quartoIn 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@quarto/jupyterlab-quartowithin 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 extensionSeeRELEASE
Package: jupyterlab-quickopen
jupyterlab-quickopenQuickly open a file in JupyterLab by typing part of its nameCompatibilityPython >=3.7.xJupyterLab>=3.2,<4.0Jupyter Server>=1.6,<2.0Configurations where notebook documents and other files reside on a filesystem local to the
Jupyter Server (which is the the default), not remote storage (e.g., S3)InstallStarting in version 1.0 of this extension, the frontend portion of this extension is pre-compiled
and included in thepipinstalled package thanks tochanges in the JupyterLab 3.0 packaging
system.To install the Jupyter Notebook server extension underPREFIX(e.g., the active virtualenv or conda
env), run the following:pipinstalljupyterlab-quickopenConfigureA Keyboard ShortcutYou can assign a keyboard shortcut to show the quickopen panel at any time. Open the keyboard editor
by clickingSettings → Advanced Settings Editor → Keyboard Shortcuts. Then enter JSON in
theUser Overridestext area like the following, adjusting thekeysvalue to assign the shortcut
of your choosing:{"shortcuts":[{"command":"quickopen:activate","keys":["Accel Ctrl P"],"selector":"body","title":"Activate Quick Open","category":"Main Area"}]}Patterns to ExcludeYou can control which files to exclude from the quick open list using Notebook server settings,
JupyterLab settings, or both.On the server side, use theContentsManager.allow_hiddenand/orContentsManager.hide_globssettings. See thedocumentation about Jupyter Notebook optionsfor details.In the JupyterLab web app, open theSettingsmenu, click theAdvanced Settings Editoroption,
select theQuick Openitem in theRaw Viewsidebar, and enter JSON in theUser Overridestext
area to override the default values.DevelopThe project includes a Makefile to aid setting up a development environment usingpython3,venv,
andpip. You must also install the latest Node LTS release as a prerequisite.# Create a dev environmentmakevenv# Activate the dev environment`makeshell`# In one terminal, watch the frontend source for changes and rebuild the extensionmakewatch# In a second terminal, run JupyterLab.`makeshell`makelabKeep an eye on the terminal runningmake watchfor TypeScript build errors. Quit and re-run themake labcommand any time you make changes to theserverextension.ReleaseMake a commit with version number bumps inpackage.json. Then do the following.# Tag the release commitgittag-a-m"0.4.0"0.4.0# Activate the dev environment`makeshell`# Build, sign, and push release to test.pypi.orgmakerelease# Build, sign and push releases to pypi.orgmakereleasePYPI_URI=pypiFAQDoes this belong in JupyterLab?Maybe. To start, I wanted to do some hacking and it's easiest to do that in a small, independent
repo. Putting this feature into JupyterLab-proper requires making the server-side portion work withContentManagersthat are not based on the local filesystem. That change might require a newContentManagerAPI since walking the file hierarchy via HTTP calls is pretty heavyweight.
Python/TypeScript tests are also required.Will this extension work with JupyterLab 2.x?Not since [version 0.5.0(https://github.com/parente/jupyterlab-quickopen/tree/0.5.0).
Package: jupyterlab-recents
jupyterlab_recentsTrack recent files and folders.RequirementsJupyterLab >= 3.0 and Notebooo >= 7.0InstallTo install the extension, execute:pipinstalljupyterlab-recentsorcondainstall-cconda-forgejupyterlab-recentsLegacy Jupyterlab v1 SupportVia NPM:jupyter labextension install jupyterlab-recents@1.0.1Or use the tagged 1.0.0 release at:https://github.com/jupyterlab-contrib/jupyterlab-recents/tree/v1.0.1UninstallTo remove the extension, execute:pipuninstalljupyterlab_recentsorcondaremovejupyterlab-recentsContributingDevelopment 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_recents 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_recentsIn 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@jlab-enhanced/recentswithin 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-remote-url
jupyterlab_remote_urlA JupyterLab extension to help set up a remote connection to the Jupyter server.This extension is composed of a Python package namedjupyterlab_remote_urlfor the server extension and a NPM package namedjupyterlab_remote_urlfor the frontend extension.RequirementsJupyterLab >= 3.6.5InstallTo install the extension, execute:pipinstalljupyterlab_remote_urlUninstallTo remove the extension, execute:pipuninstalljupyterlab_remote_urlTroubleshootIf 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_remote_url directory# Install package in development modepipinstall-e"."# Link your development version of the extension with JupyterLabjupyterlabextensiondevelop.--overwrite# Server extension must be manually installed in develop modejupyterserverextensionenablejupyterlab_remote_url# 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_remote_url
pipuninstalljupyterlab_remote_urlIn 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_remote_urlwithin that folder.Packaging the extensionSeeRELEASE
Package: jupyterlab-reset-fixer
jupyterlab_reset_fixerIt fixes regex pattern for reset-on-load command.reset=also triggers workspace reset.Requirements0.*.*JupyterLab >= 3.01.*.*JupyterLab >= 4.01.* versions are developed and tested with JupyterLab 4.0.0a29.InstallTo install the extension, execute:pipinstalljupyterlab_reset_fixerUninstallTo remove the extension, execute:pipuninstalljupyterlab_reset_fixerContributingCreating Conda EnvironmentFor0.*.*versions,conda create -n jupyterlab-ext --override-channels --strict-channel-priority -c conda-forge -c nodefaults jupyterlab=3 cookiecutter nodejs jupyter-packaging gitDevelopment 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_reset_fixer 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_reset_fixerIn 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-reset-fixerwithin 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 extensionSeeRELEASE