jupyterlab_blockly_polyglot_extension
A JupyterLab extension implementing a Blockly palette for multiple programming languages.
Data science training materials in Python using this extension are here and matched versions for R are here.
The following query string parameters enable functionality that is useful for classroom instruction and/or research:
- bl=py forces the extension to display on load (it is already active)
- log=xxx specifies a url for a logging endpoint (e.g. https://yourdomain.com/log)
- id=xxx adds an identifier for logging
Requirements
- JupyterLab >= 4.0.0
Later versions of JupyterLab changed the command UI. See here for the options to launch the extension
Install
To install the extension, execute:
pip install jupyterlab_blockly_polyglot_extension
Uninstall
To remove the extension, execute:
pip uninstall jupyterlab_blockly_polyglot_extension
Contributing
- Andrew Olney
- Luiz Barboza
Development install
Creating a virtual environment is recommended:
curl -L -O "https://github.com/conda-forge/miniforge/releases/latest/download/Miniforge3-$(uname)-$(uname -m).sh"
bash Miniforge3-$(uname)-$(uname -m).sh
!!! Edit the environment.yml file to change the environment name as you like !!!
mamba env create -f environment.yml
/home/ubuntu/miniforge3/bin/mamba init
mamba activate <NAME>
Note: This extension is designed to use a language server. It will work without a language server, but functionality will be reduced. See here to install language servers for the languages you want to use.
The jlpm command is JupyterLab's pinned version of
yarn that is installed with JupyterLab. You may use
yarn or npm in lieu of jlpm below, but don't do it unless you really know what you're doing.
# Clone the repo to your local environment
# Change directory to the jupyterlab_blockly_polyglot_extension directory
# Install package in development mode
pip install -e "."
# Link your development version of the extension with JupyterLab
jupyter labextension develop . --overwrite
# Rebuild extension Typescript source after making changes
jlpm build
You 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 needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab
The watch.sh script runs JupyterLab in watch mode with the Chrome browser
With 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, the jlpm build command 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:
jupyter lab build --minimize=False
Development uninstall
pip uninstall jupyterlab_blockly_polyglot_extension
In development mode, you will also need to remove the symlink created by jupyter labextension develop
command. To find its location, you can run jupyter labextension list to figure out where the labextensions
folder is located. Then you can remove the symlink named jupyterlab-blockly-polyglot-extension within that folder.
Testing the extension
Frontend tests
This extension is using Jest for JavaScript code testing.
To execute them, execute:
jlpm
jlpm test
Integration tests
This extension uses Playwright for the integration tests (aka user level tests). More precisely, the JupyterLab helper Galata is used to handle testing the extension in JupyterLab.
More information are provided within the ui-tests README.
Packaging the extension
See RELEASE
Metadata
Release files for jupyterlab-blockly-polyglot-extension 1.1.6
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| jupyterlab_blockly_polyglot_extension-1.1.6.tar.gz | 721.1 kB | Without provenance | Details for jupyterlab_blockly_polyglot_extension-1.1.6.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| jupyterlab_blockly_polyglot_extension-1.1.6-py3-none-any.whl | Python 3 | none | any | Details for jupyterlab_blockly_polyglot_extension-1.1.6-py3-none-any.whl |
Total release size: 1.1 MB
Release files / jupyterlab_blockly_polyglot_extension-1.1.6.tar.gz
| Download URL | jupyterlab_blockly_polyglot_extension-1.1.6.tar.gz |
|---|---|
| Size | 721.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
db69cd5a001b41f700836a3528ed97400f8487670ff0f6b8d95bc511347faf01
|
|
BLAKE2b-256 checksum How to use checksums |
b55e70fb7761b4867fc0197028e45b167e372a09716f809b8f0076bff84e0f68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Release files / jupyterlab_blockly_polyglot_extension-1.1.6-py3-none-any.whl
| Download URL | jupyterlab_blockly_polyglot_extension-1.1.6-py3-none-any.whl |
|---|---|
| Size | 382.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0f59cddda6dcc57b35003c5ae640d8eeaa92a3f553bf2c1d15c109dcd5e64326
|
|
BLAKE2b-256 checksum How to use checksums |
6cfd0606ade396f5a2e9e715d525148fd4977ba7f46552ac5bff8a9a3a3e768b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.6
|
Security for jupyterlab-blockly-polyglot-extension 1.1.6
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.