trelis
A JupyterLab Code Assistant
Requirements
- JupyterLab >= 4.0.0
- Node >= 22.6
- Yarn
Install
To install the extension, execute:
pip install trelis
to install with node and yarn (for example, in a remote GPU server like RunPod), first run:
import os
import subprocess
def check_node_yarn():
# Check if Node.js is installed
try:
node_version = subprocess.check_output(["node", "--version"]).decode().strip()
print(f"Node.js is installed: {node_version}")
except FileNotFoundError:
print("Node.js is not installed.")
install_node()
# Check if Yarn is installed
try:
yarn_version = subprocess.check_output(["yarn", "--version"]).decode().strip()
print(f"Yarn is installed: {yarn_version}")
except FileNotFoundError:
print("Yarn is not installed.")
install_yarn()
def install_node():
print("Installing Node.js...")
# Download Node.js binary (you can change the version if needed)
os.system("curl -O https://nodejs.org/dist/v22.6.0/node-v22.6.0-linux-x64.tar.xz --silent")
# Extract Node.js
os.system("tar -xf node-v22.6.0-linux-x64.tar.xz --no-same-owner")
# Add Node.js to the PATH for the current notebook session
node_bin_path = os.path.abspath("node-v22.6.0-linux-x64/bin")
os.environ['PATH'] = node_bin_path + ":" + os.environ['PATH']
print(f"Node.js installed to {node_bin_path}")
# Verify installation
node_version = subprocess.check_output(["node", "--version"]).decode().strip()
print(f"Node.js version: {node_version}")
def install_yarn():
print("Installing Yarn...")
# Install Yarn via script
os.system("curl -o- -L https://yarnpkg.com/install.sh | bash")
# Add Yarn to the PATH for the current notebook session
yarn_bin_path = os.path.expanduser("~/.yarn/bin")
os.environ['PATH'] = yarn_bin_path + ":" + os.environ['PATH']
print(f"Yarn installed to {yarn_bin_path}")
# Verify installation
yarn_version = subprocess.check_output(["yarn", "--version"]).decode().strip()
print(f"Yarn version: {yarn_version}")
# Run the check and installation process
check_node_yarn()
Uninstall
To remove the extension, execute:
pip uninstall trelis
Contributing (Private)
Development install
Note: You will need NodeJS to build the extension package.
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.
First:
conda create -n jupyterlab-ext --override-channels --strict-channel-priority -c conda-forge -c nodefaults jupyterlab=4 nodejs=20 git copier=9 jinja2-time
then:
conda activate jupyterlab-ext
Or just:
cd trelis-jupyter-assistant
python -m venv jupyterlab-ext
source jupyterlab-ext/bin/activate
Then:
Then, run:
npm install -g yarn yarn install pip install -ve . jupyter labextension develop --overwrite . pip install jupyterlab jlpm jlpm build jlpm watch
This will watch the source directory and allow you to run JupyterLab at the same time in different terminals to watch for changes in the extension's source and automatically rebuild the extension.
```bash
# Watch the source directory in one terminal, automatically rebuilding when needed
jlpm watch
# Run JupyterLab in another terminal
jupyter lab
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 trelis
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 trelis-jupyter-assistant 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 trelis 1.3.0
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 | |
|---|---|---|---|---|
| trelis-1.3.0.tar.gz | 170.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| trelis-1.3.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 197.5 kB
Release files / trelis-1.3.0.tar.gz
| Download URL | trelis-1.3.0.tar.gz |
|---|---|
| Size | 170.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dacfadce08ed42928e9fdec172b170cc02249344e84b8fefb726f90a3c92b643
|
|
BLAKE2b-256 checksum How to use checksums |
917491c5341a21dcfb2b09992f3fa8d185b90e0389ef5d4b4e7ac79f6f260a56
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Release files / trelis-1.3.0-py3-none-any.whl
| Download URL | trelis-1.3.0-py3-none-any.whl |
|---|---|
| Size | 26.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e90d379c1204900998c3747e728fb2c94258662dc0c116e20f03e16b63c7273a
|
|
BLAKE2b-256 checksum How to use checksums |
b0a33f8cde4f7aa685924e597c40b15a332722370a686a3e4e3497d5e8525a84
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.6
|
Security for trelis 1.3.0
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.