Skip to main content

Literate package development with Jupyter

Project description

Literary

pypi-badge binder-badge

This package is an exploration of the literate programming idea pioneered by Donald Knuth and implemented in the nbdev package. Although nbdev looks to be a very mature and comprehensive tool, it is quite opinionated. This package is an investigation into what a smaller nbdev might look like.

Philosophy

  1. Low mental overhead
    Realistically, most Python programmers that wish to write packages need to have some familiarity with the Python package development model, including the conventional structure of a package. For this reason, I feel that it is important to design literary such that these skills translate directly to designing libraries with notebooks
  2. Minimal downstream impact
    Users of literary packages should not realise that they are consuming notebook-generated code at runtime. This means that a pure-Python package needs to be generated from the notebooks, and it must use the conventional import model. For this reason, literary should only exist as a development dependency of the package.

Differences with nbdev

  • Use of cell tags instead of comments or magics to dictate exports
  • Use of nbconvert machinery to build the pure-Python lib package
  • Use of import hooks to import other notebooks
    • Maintains a similar programming model to conventional module development
    • Reduces the need to modify notebook contents during conversion
  • Minimal runtime overhead
    • Features like patch are removed from the generated module (& imported notebook source) using AST transformations
  • Currently no documentation generation
    • Loosely, the plan is to use existing notebook-book tooling to re-use the existing Jupyter ecosystem

Design

The plan for this package is:

  1. Notebooks will be written inside <PACKAGE_NAME>/ in literary project's root directory
  2. Notebooks will respect relative imports and other pure-Python features to minimise the differences between the generated packages and the notebooks
  3. A pure-python generated lib/<PACKAGE_NAME>/ directory will be built before Poetry builds the final project.
    E.g.
    [tool.poetry]
    # ...
    packages = [
      { include = "<PACKAGE_NAME>", from = "lib" },
    ]
    

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

literary-1.3.0.tar.gz (10.9 kB view details)

Uploaded Source

Built Distribution

literary-1.3.0-py3-none-any.whl (13.7 kB view details)

Uploaded Python 3

File details

Details for the file literary-1.3.0.tar.gz.

File metadata

  • Download URL: literary-1.3.0.tar.gz
  • Upload date:
  • Size: 10.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.4 CPython/3.8.5 Linux/5.4.0-54-generic

File hashes

Hashes for literary-1.3.0.tar.gz
Algorithm Hash digest
SHA256 ccbfb80c33620cc32661b59a8285835df85a8ae754ae9ea82f15578d97f34214
MD5 c44b77e109f81459fcc8b3bffed13b29
BLAKE2b-256 096dbb9740a8d8cbef99fe3cb13fc2824fe086bdea36898efb025016e6c34d5a

See more details on using hashes here.

File details

Details for the file literary-1.3.0-py3-none-any.whl.

File metadata

  • Download URL: literary-1.3.0-py3-none-any.whl
  • Upload date:
  • Size: 13.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: poetry/1.1.4 CPython/3.8.5 Linux/5.4.0-54-generic

File hashes

Hashes for literary-1.3.0-py3-none-any.whl
Algorithm Hash digest
SHA256 c5dd2fab5c778d97771422f1ccdf0cb7e07fefb2e482c8dad794bae319efaebc
MD5 0d481334e608d3cd1608d9cdd6bd601a
BLAKE2b-256 819351b319c808c0d9c8bcf47408314e159c5f42c6b1d73395e81f60b1182777

See more details on using hashes here.

Supported by

AWS AWS Cloud computing and Security Sponsor Datadog Datadog Monitoring Fastly Fastly CDN Google Google Download Analytics Microsoft Microsoft PSF Sponsor Pingdom Pingdom Monitoring Sentry Sentry Error logging StatusPage StatusPage Status page