live-qna-jupyterlab
JupyterLab extension for opening the existing Live QnA server inside JupyterLab as a floating overlay or left sidebar panel.
Quick install
End users
Once published to PyPI, install it with:
pip install live-qna-jupyterlab
Then restart JupyterLab.
Shared server / JupyterHub admins
Install the package once into the Python environment that runs JupyterLab:
pip install live-qna-jupyterlab
All users on that environment can use the extension after JupyterLab restarts.
Local install from this repository
cd jupyterlab-extension
./scripts/build-dist.sh
pip install dist/*.whl
If you are not publishing to PyPI yet, sharing the built wheel from dist/ is the easiest way for other people to install the extension.
What it includes
- Top-area quick access button
- Floating overlay with embedded iframe
- Optional left sidebar panel
- Settings for server URL, auto-open, and visibility options
Settings
Open JupyterLab Settings Editor and adjust this plugin:
serverUrl: Live QnA URL (default:https://qna.baeum.ai.kr)showTopButton: top quick-access 버튼 표시 여부showLeftPanel: left sidebar tab 표시 여부autoOpen: JupyterLab 복원 후 자동 오픈 여부openMode:floating또는left
Example user settings file:
{
"serverUrl": "https://qna.baeum.ai.kr",
"showTopButton": true,
"showLeftPanel": true,
"autoOpen": false,
"openMode": "left"
}
Development
cd jupyterlab-extension
npm ci
npm run build
Build a distributable wheel
cd jupyterlab-extension
./scripts/build-dist.sh
This only requires uv; the Python build environment will install the packaging/build dependencies automatically.
It produces a Python wheel/sdist in dist/. The wheel is the easiest artifact to share with other users.
GitHub Actions
python-package.ymlbuilds wheel/sdist on PRs, pushes, and tags.- Tagging
v*also prepares the workflow for optional PyPI publishing. - To enable PyPI publishing, set the repository variable
PUBLISH_TO_PYPI=trueand configure PyPI trusted publishing for this repository.
Notes
- The extension uses direct server URL mode.
- Default Live QnA URL:
https://qna.baeum.ai.kr
Metadata
Release files for live-qna-jupyterlab 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 | |
|---|---|---|---|---|
| live_qna_jupyterlab-0.1.0.tar.gz | 54.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| live_qna_jupyterlab-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 73.4 kB
Release files / live_qna_jupyterlab-0.1.0.tar.gz
| Download URL | live_qna_jupyterlab-0.1.0.tar.gz |
|---|---|
| Size | 54.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
823068adc40d171a4cb88091a4a3e6fce976fe40a1636d6f920c71a83e712865
|
|
BLAKE2b-256 checksum How to use checksums |
91052f8461e4605f650de3f540582f7b167d1a057b6c99103e6e8cfb2b3660b6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / live_qna_jupyterlab-0.1.0-py3-none-any.whl
| Download URL | live_qna_jupyterlab-0.1.0-py3-none-any.whl |
|---|---|
| Size | 18.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
583ebb3fd09fa3d770386b99470072068028de10a58bfe85141efd380c861191
|
|
BLAKE2b-256 checksum How to use checksums |
949a97872a7e611497c761a8e93a63cb58d167b1e6fbd9e86078aa7cef5db953
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for live-qna-jupyterlab 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.