Stellars JupyterLab Fixes
Metapackage that installs all Stellars JupyterLab fixes in one command.
These fixes address papercuts and annoyances in JupyterLab 4 that were bothering us enough to do something about them. They are intended as temporary workarounds until the JupyterLab team incorporates proper solutions into the mainline - at which point this repo will happily become obsolete.
Yes, we wrote an entire metapackage just to fix scroll positions and font alignments. No, we don't have better things to do. Okay, we do, but here we are.
Installation
pip install stellars_jupyterlab_fixes
Included Fixes
- jupyterlab_change_ui_font_size_fix - Fix file browser alignment when changing UI font size
- jupyterlab_file_browser_column_width_fix - Keep file browser names visible when the cached column width is stale
- jupyterlab_jump_to_definition_fix - Fix "jump to definition" for notebooks using Jedi in kernel environment
- jupyterlab_markdown_switch_tab_scrolling_fix - Prevent markdown scroll drift when switching tabs
- jupyterlab_markdown_syntax_rendering_fix - Restore syntax-highlight colours in rendered Markdown fenced code blocks when no editor is open
- jupyterlab_markdown_viewer_toc_fix - Fix broken TOC navigation and anchor links in Markdown Viewer
- jupyterlab_other_file_type_menu_fix - Fix broken context menu for unregistered file types (LICENSE, .gitignore, Dockerfile)
- jupyterlab_restore_terminals_fix - Restore terminals' original working directories after workspace restore
- jupyterlab_server_proxy_launcher_fix - Fix SVG icon display for jupyter-server-proxy launchers in custom categories
- jupyterlab_terminal_cpr_escape_fix - Fix CPR escape sequences appearing as literal text in idle terminals
Requirements
- JupyterLab >= 4.0.0
- Python >= 3.9
Metadata
Release files for stellars-jupyterlab-fixes 1.0.17
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 |
|---|---|---|---|---|
| stellars_jupyterlab_fixes-1.0.17.tar.gz | 6.2 kB | Without provenance | Details for stellars_jupyterlab_fixes-1.0.17.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| stellars_jupyterlab_fixes-1.0.17-py3-none-any.whl | Python 3 | none | any | Details for stellars_jupyterlab_fixes-1.0.17-py3-none-any.whl |
Total release size: 9.0 kB
Release files / stellars_jupyterlab_fixes-1.0.17.tar.gz
| Download URL | stellars_jupyterlab_fixes-1.0.17.tar.gz |
|---|---|
| Size | 6.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2e351b37b988e851eec90d498d2b83d8a6dcb2c5a0f39cfcf259bd54af6133cb
|
|
BLAKE2b-256 checksum How to use checksums |
0ba3421364058a9699554294367d444f3457e9b832273d1f41861972beef0449
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Release files / stellars_jupyterlab_fixes-1.0.17-py3-none-any.whl
| Download URL | stellars_jupyterlab_fixes-1.0.17-py3-none-any.whl |
|---|---|
| Size | 2.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
627c9b8a51a0c13f2575f997e3ddc46efa9d38e202d8d1b02afb906fd2c7996f
|
|
BLAKE2b-256 checksum How to use checksums |
ee9ebcfc0f87ff08da19a2daa2ecebe1c51e5653351f1683ea0af3d8401f96be
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.14.10
|
Security for stellars-jupyterlab-fixes 1.0.17
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.