kts_dark_theme
Dark theme for Knowing the Sky. Experimental, not yet for distribution.
dev environment setup
Create a conda environment with at least:
jupyterlab>=4.3.1jupyterlab-mystpythonnodejs=22(do not use your system node)
make is also required.
If you have the dependencies for Knowing The Sky installed, the only additional
requirement is nodejs=22.
Do not install hatch-jupyter-builder.
dev installation
initial
run make build && make install. This will download all node dependencies,
perform an initial build of the extension, and symlink it to the central
Jupyter extensions directory. Now the extension should be available in
JupyterLab, and changes you make to
kts_dark_theme/labextension/themes/kts-dark-theme/index.css will appear
in JupyterLab on page reload.
rebuild
If you want to ship changes to the theme, run make rebuild. This
will propagate changes from kts_dark_theme/labextension/themes/kts-dark-theme/index.css
into the non-editable ("regular") version of the extension.
reinstall/relink
If your links get messed up somehow such that you can't rebuild the
package or Jupyter can't find your editable CSS, run make reinstall.
Do not attempt to relink by directly reinstalling the package with pip.
The Lab extension build sequence will cause this to fail.
full reinstall
Run make clean && make build && make install.
A note on PyCharm
The package includes ESLint configurations, which PyCharm will attempt to
automatically use. It will probably fail unless you have all the correct
node packages and a compatible .stylelintrc available at system level. This will
create annoying error messages when editing many files. To fix this, you can
either install them at system level or go to Settings/Stylelint and point it
to the node module jlpm installed when you did the initial install:
node_modules/stylelint (relative to repo root)
Metadata
Release files for kts-dark-theme 0.1.2
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 |
|---|---|---|---|---|
| kts_dark_theme-0.1.2.tar.gz | 12.7 kB | Without provenance | Details for kts_dark_theme-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| kts_dark_theme-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for kts_dark_theme-0.1.2-py3-none-any.whl |
Total release size: 28.6 kB
Release files / kts_dark_theme-0.1.2.tar.gz
| Download URL | kts_dark_theme-0.1.2.tar.gz |
|---|---|
| Size | 12.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c04a61a5603c16f4046253ec1b255c023d0bb4788289e304d034bb0e90db9fc6
|
|
BLAKE2b-256 checksum How to use checksums |
2491b4b0fb346c4f594e9db1e30b56d7fa6467eee3e65ff21c47e7bf4302fd50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Release files / kts_dark_theme-0.1.2-py3-none-any.whl
| Download URL | kts_dark_theme-0.1.2-py3-none-any.whl |
|---|---|
| Size | 16.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
525f60865f820051662483b6e06d2a30cac315336a84a354a4e94815fa9ae4a7
|
|
BLAKE2b-256 checksum How to use checksums |
7c9c06f46fffcedca0e08e9b515d67e7fb0ff2695a67d13dc89ff37ec9c2ea04
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.11
|
Security for kts-dark-theme 0.1.2
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.