check-execution-order
A tool and pre-commit hook to automatically check execution order in Jupyter Notebooks.
Installation
$ pip install check-execution-order
Usage as a pre-commit hook (recommended)
See pre-commit for instructions
Sample .pre-commit-config.yaml:
- repo: https://github.com/MarcoGorelli/check-execution-order
rev: v0.1.1
hooks:
- id: check-execution-order
Command-line example
$ check-execution-order bad.ipynb
Cell 1 comes after 2 in file 'bad.ipynb'
Configuration
None yet. Got any requests? Please let me know!
1 maintainer
Metadata
1 maintainer
Release files for check-execution-order 0.1.1
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 |
|---|---|---|---|---|
| check_execution_order-0.1.1.tar.gz | 3.2 kB | Without provenance | Details for check_execution_order-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| check_execution_order-0.1.1-py2.py3-none-any.whl | Python 2, Python 3 | none | any | Details for check_execution_order-0.1.1-py2.py3-none-any.whl |
Total release size: 6.8 kB
Release files / check_execution_order-0.1.1.tar.gz
| Download URL | check_execution_order-0.1.1.tar.gz |
|---|---|
| Size | 3.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ffbf31b98c3b7db255892a89e31fd1683bf26bcc04285501696ccb4e5864ec0c
|
|
BLAKE2b-256 checksum How to use checksums |
531d9eab0494ce5c448c51562dd2ab824ca1b6e1722c8f5c0ca573f3d7ad722e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.5
|
Release files / check_execution_order-0.1.1-py2.py3-none-any.whl
| Download URL | check_execution_order-0.1.1-py2.py3-none-any.whl |
|---|---|
| Size | 3.6 kB |
| Tags | Python 2 Python 3 |
|
SHA-256 checksum How to use checksums |
5c7d6ad0e52519ca2538bac8cdbf7cd737ff61e1aa6eb3911ec3988d90dc090c
|
|
BLAKE2b-256 checksum How to use checksums |
e35b63184a1df2e8c1fcc174590d4dc3b5ed6945f879440463168192d261c5f1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/3.10.0 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.59.0 CPython/3.8.5
|
Security for check-execution-order 0.1.1
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.
