nbprocess
This will become v2 of nbdev in the near-ish future.
Install
With pip:
pip install nbprocess
With conda:
conda install -c fastai nbprocess
How to use
By default docs are exported for use with Quarto.
To install Quarto on Ubuntu, run nbprocess_install. See the Quarto
docs for other platforms.
You can run nbprocess_help from the terminal to see a list of all CLI
tools:
!nbprocess_help
nbprocess_bump_version Increment version in `settings.py` by one
nbprocess_clean Clean all notebooks in `fname` to avoid merge conflicts
nbprocess_conda Create and upload a conda package.
nbprocess_create_config Creates a new config file for `lib_name` and `user` and saves it.
nbprocess_deploy Deploy docs to GitHub Pages.
nbprocess_docs Generate the docs.
nbprocess_export Export notebooks in `path` to python modules
nbprocess_filter A notebook filter for quarto
nbprocess_fix Create working notebook from conflicted notebook `nbname`
nbprocess_ghp_deploy Deploy docs in doc_path from settings.ini to GitHub Pages
nbprocess_help Show help for all console scripts
nbprocess_install Install quarto and the current library.
nbprocess_install_hooks Install git hooks to clean/trust notebooks automatically
nbprocess_install_quarto Installs latest quarto on mac or linux. Prints instructions for Windows.
nbprocess_migrate_directives Convert all directives in `fname` from v1 to v2.
nbprocess_new Create a new project from the current git repo
nbprocess_prepare Export notebooks to python modules, test code and clean notebooks.
nbprocess_preview Start a local docs webserver.
nbprocess_pypi Create and upload python package to pypi.
nbprocess_quarto Create quarto docs and README.md
nbprocess_release Release both conda and pypi packages.
nbprocess_sidebar Create sidebar.yml
nbprocess_test Test in parallel the notebooks matching `fname`, passing along `flags`
nbprocess_trust Trust notebooks matching `fname`
nbprocess_update Propagates any change in the modules matching `fname` to the notebooks that created them
Metadata
Release files for nbprocess 0.0.7
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 |
|---|---|---|---|---|
| nbprocess-0.0.7.tar.gz | 39.9 kB | Without provenance | Details for nbprocess-0.0.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| nbprocess-0.0.7-py3-none-any.whl | Python 3 | none | any | Details for nbprocess-0.0.7-py3-none-any.whl |
Total release size: 84.5 kB
Release files / nbprocess-0.0.7.tar.gz
| Download URL | nbprocess-0.0.7.tar.gz |
|---|---|
| Size | 39.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c8bf60ec2ce2e01ef408efb632f75f8c59ec9edbaa4499884cde54dafc22b214
|
|
BLAKE2b-256 checksum How to use checksums |
5ef6e08f144ff6a16212c96df92ff0b652df0aa3612f454d0b865e3a269845fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.10
|
Release files / nbprocess-0.0.7-py3-none-any.whl
| Download URL | nbprocess-0.0.7-py3-none-any.whl |
|---|---|
| Size | 44.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f69aa377da13e6fc8c6f1a6bc487dbf7641c2b89e4209bf469acb59008d7203e
|
|
BLAKE2b-256 checksum How to use checksums |
4afb218263ade63994ef19b941e8df2feee6362942adc8c6e429e206810f6f77
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.9.10
|
Security for nbprocess 0.0.7
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.