➤ nbsafety
About
nbsafety adds a layer of protection to computational notebooks by solving the
stale dependency problem when executing cells out-of-order. Here's an
example in action:
When the first cell is rerun, the second cell now contains a reference to an
updated f and is suggested for re-execution with a turquoise highlight. The
third cell contains a reference to a stale y -- y is stale due to its
dependency on an old value of f. As such, the third cell is marked as unsafe
for re-execution with a red highlight. Once the second cell is rerun, it is
now suggested to re-execute the third cell in order to refresh its stale
output.
nbsafety accomplishes its magic using a combination of a runtime tracer (to
build the implicit dependency graph) and a static checker (to provide warnings
before running a cell), both of which are deeply aware of Python's data model.
In particular, nbsafety requires minimal to no changes in user
behavior, opting to get out of the way unless absolutely necessary and letting
you use notebooks the way you prefer.
Install
pip install nbsafety
Interface
The kernel ships with an extension that highlights cells with live references to stale symbols using red UI elements. It furthermore uses turquoise highlights for cells with live references to updated symbols, as well as for cells that resolve staleness.
Running
To run an nbsafety kernel in Jupyter, select "Python 3 (nbsafety)" from the
list of notebook types in Jupyter's "New" dropdown dialogue. For JupyterLab,
similarly select "Python 3 (nbsafety)" from the list of available kernels in
the Launcher tab.
| Jupyter Notebook Entrypoint: | Jupyter Lab Entrypoint: |
|---|---|
Uninstall
pip uninstall nbsafety
License
Code in this project licensed under the BSD-3-Clause License.
➤ Contributors
| Stephen Macke | Ray Gong | Shreya Shankar |
Metadata
Release files for nbplus 0.0.80
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 |
|---|---|---|---|---|
| nbplus-0.0.80.tar.gz | 150.4 kB | Without provenance | Details for nbplus-0.0.80.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nbplus-0.0.80-py2.py3-none-any.whl | Python 3, Python 2 | none | any | Details for nbplus-0.0.80-py2.py3-none-any.whl |
Total release size: 314.7 kB
Release files / nbplus-0.0.80.tar.gz
| Download URL | nbplus-0.0.80.tar.gz |
|---|---|
| Size | 150.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f598f35aaabc4ba9bc6548ef0b6563205c9ff4bb366230c6ec5ecf72c065beac
|
|
BLAKE2b-256 checksum How to use checksums |
97226a5a25069da4922d12f00bb64638d9b3ea03f32a6008988bd6a3e987c3bb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.7
|
Release files / nbplus-0.0.80-py2.py3-none-any.whl
| Download URL | nbplus-0.0.80-py2.py3-none-any.whl |
|---|---|
| Size | 164.3 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
b50b73b81879961139c50837aeef856c49b9172297ec96497e1b3a88e1cd8cf9
|
|
BLAKE2b-256 checksum How to use checksums |
c8f2d89e0d10eab10c1005b5e1b40f4821d44b497469df9841f1f7519dd73be4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.2.0 pkginfo/1.6.1 requests/2.25.1 setuptools/51.0.0 requests-toolbelt/0.9.1 tqdm/4.54.1 CPython/3.9.7
|
Security for nbplus 0.0.80
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.