GW-BASIC Jupyter kernel
Run GW-BASIC programs in JupyterLab or Notebook. Variables and program lines persist between cells. The kernel converts the interpreter's Sixel output to inline PNG images, so the notebook browser does not need Sixel support.
Requires Python 3.10 or later and the native GW-BASIC 2026 interpreter on Linux or macOS. The Python package does not include that interpreter. The DOS executables cannot be used as the notebook backend.
Install the interpreter
With Homebrew on Linux or macOS:
brew tap evvaletov/gwbasic https://github.com/evvaletov/gw-basic-2026.git
brew install evvaletov/gwbasic/gwbasic
The Homebrew formula builds from a pinned source revision. It includes the interpreter and native compiler, with PulseAudio disabled.
Alternatively, build from source with a C11 compiler and CMake:
git clone https://github.com/evvaletov/gw-basic-2026.git
cd gw-basic-2026
cmake -S . -B build -DCMAKE_BUILD_TYPE=Release
cmake --build build --parallel 2
export GWBASIC="$PWD/build/gwbasic"
Install the kernel
Create a Python environment for the kernel and JupyterLab:
python3 -m venv .venv
. .venv/bin/activate
python -m pip install gwbasickernel jupyterlab
gwbasickernel-install --sys-prefix
jupyter lab
Choose GW-BASIC 2026 when creating a notebook. The kernel looks for the
interpreter in GWBASIC, then on PATH. To save its location in the kernelspec,
use this command instead of the installer command above:
gwbasickernel-install --sys-prefix --gwbasic /absolute/path/to/gwbasic
If Jupyter runs in another Python environment, use --user to register the
kernel for your account. Keep the kernel's Python environment in place:
the kernelspec records its Python executable.
Try it
10 FOR N=1 TO 8
20 PRINT N;N*N
30 NEXT N
RUN
For graphics, clear the previous program first:
NEW
10 SCREEN 1
20 CIRCLE (160,100),80,2
RUN
See the executed graphics notebook and demo guide.
%new clears the BASIC program; %reset starts a fresh interpreter process.
%timeout 60 changes the output wait timeout from its default of 30 seconds.
Metadata
Release files for gwbasickernel 0.1.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 | Actions |
|---|---|---|---|---|
| gwbasickernel-0.1.0.tar.gz | 19.1 kB | Without provenance | Details for gwbasickernel-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| gwbasickernel-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for gwbasickernel-0.1.0-py3-none-any.whl |
Total release size: 35.2 kB
Release files / gwbasickernel-0.1.0.tar.gz
| Download URL | gwbasickernel-0.1.0.tar.gz |
|---|---|
| Size | 19.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d8bcb4848bf675b45494cbb8d05e681d3892a9500ff6f5add83146572c70692e
|
|
BLAKE2b-256 checksum How to use checksums |
e878633c79074d292543430f14d8ad024d79b326beb506809a4b6c7dc9d96ee7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Release files / gwbasickernel-0.1.0-py3-none-any.whl
| Download URL | gwbasickernel-0.1.0-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
72134e338a82848b409f58bd7867e51748ce91305e3db2548d84cd49c5bdf09f
|
|
BLAKE2b-256 checksum How to use checksums |
45baeb6070095ca622784f8e21ea727e491419536e7e8b491d91a053f54b9e5c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.15
|
Security for gwbasickernel 0.1.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.