AfterPython: Python Package Maintenance Toolkit and Project Website Generator
Problem
Going from writing Python code to publishing and maintaining a package is time-consuming. First-time maintainers must learn multiple tools and concepts, e.g. MyST, SemVer, CI/CD (pre-commit hooks, GitHub workflows), and they often spend hours just to deploy a documentation site whereas well-resourced projects like PyTorch and Scikit-Learn have dedicated websites that serve as their project hubs.
Solution
afterpython automates the tedious parts of Python package maintenance and generates a project website for building community and hosting content such as documentation, blog posts, tutorials, examples and more — empowering more developers to write packages with ease.
afterpython is a CLI tool that abstracts away the complexity of content writing, website deployment, and package release/maintenance by providing an opinionated set of modern tools — so you don’t have to spend time selecting or learning anything beyond the basics.
Core Features
- Write content directly in MyST Markdown, Jupyter Notebook or marimo notebooks, with reproducible outputs for marimo
- Go from writing to website deployment in minutes — no need to learn any of the underlying tools
- Centralize all your content in a modern, unified project website — from documentation to blog posts
- Zero-config orchestration — Pre-configured modern tooling with sane defaults (see Tech Stack), so you can start maintaining packages immediately without learning each tool
- ⚡ Full-text search across ALL your content in your website — docs, blogs, tutorials, everything
- Export content as PDF — for example, combine all blog posts into a single PDF file
- 🤖 Embedded AI Chatbot that answers questions directly using an in-browser LLM — at no cost
Project Website
The project website for
afterpythonis created usingafterpythonitself. See the website.
You can create your own website too and deploy it to GitHub Pages in less than a minute! See Quickstart.
Installation
# install afterpython as a dev dependency
uv add --dev afterpython
# initialize afterpython
ap init
CLI Commands
# show all commands
ap --help
# or use terminal UI (TUI)
ap tui
Tech Stack
Metadata
Release files for afterpython 0.4.3
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 |
|---|---|---|---|---|
| afterpython-0.4.3.tar.gz | 87.9 kB | Without provenance | Details for afterpython-0.4.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| afterpython-0.4.3-py3-none-any.whl | Python 3 | none | any | Details for afterpython-0.4.3-py3-none-any.whl |
Total release size: 201.8 kB
Release files / afterpython-0.4.3.tar.gz
| Download URL | afterpython-0.4.3.tar.gz |
|---|---|
| Size | 87.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a391c2f664c29d227b76375b0ad0c153bc1961b1370678fa9dd50b697f03fc03
|
|
BLAKE2b-256 checksum How to use checksums |
dabfcf1afe959d2f673c3c91b1ce98d20aa3d629e68287616711f516d37c0af1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / afterpython-0.4.3-py3-none-any.whl
| Download URL | afterpython-0.4.3-py3-none-any.whl |
|---|---|
| Size | 113.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
34186bcf9dfc4fd00652c21961547a076d94e980e4a42d0ed9b03e48c65576ee
|
|
BLAKE2b-256 checksum How to use checksums |
f09f35c3e3d50775293c7c325b7fb42f5853ecf61922fc8a4cbdb62bd182da13
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for afterpython 0.4.3
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.