pypackitup - Python Package Template
Template repository for developing Python packages.
Do you like the Python Package Template? Star the repository on GitHub and please consider helping support its ongoing development:
READ THE DOCS HERE!
Detailed documentation can be found at https://pypackitup.wrencode.dev.
Table of Contents
About
The Python Package Template is an example for Python package development.
Dependencies
The Python Package Template does not have any third-party dependencies to run the code. It has several development dependencies, which can be seen in the package pyproject.toml.
Toolchain
The below tools and resources are used as part of pypackitup:
- uv - package management
- ruff - code linting
- bandit - code security
- make - Makefile build automation
- MkDocs - package documentation
- python-dotenv - programmatic access to environment variables defined in a
.envfile - pytest - code testing framework
- GitHub Actions - CI/CD
- act - GitHub Actions testing
Setup
The below list covers all updates needed in the Python Package Template when using it to create a new Python package:
Configuration
pyproject.toml: Update all relevant fields as needed for the new package.
Version Control
.gitignore: Add any package-specific files that should not be checked in to version control..github/ISSUE_TEMPLATE/: Make any package-specific changes to the project issue templates..github/workflows/python-package.yml: Update the supported Python versions and add any necessary CI/CD steps.
Documentation
README.md: Update theREADME.mdwith all necessary package documentation.mkdocs.yml: Update thenavsection with all necessary pages and their corresponding Markdown files (see below).docs-mkdocs/CNAME: Update theCNAMEfile with the desired mkdocs documentation GitHub Pages custom domain.docs-mkdocs/extra.css: Add any custom CSS for the mkdocs documentation.docs-mkdocs/extra.js: Add any custom JavaScript for the mkdocs documentation.docs-mkdocs/*.md: Add any necessary Markdown (.md) files for pages in the mkdocs documentation.docs-mkdocs/*.svg/*.png/*.jpg/etc.: Add any necessary images for the mkdocs documentation.
Environment
.env: Create a.envfile from the provided.env.templatefile (runcp .env.template .envin the command line) and add any necessary package environment variables.
Code
src/pypackitup/: Rename the source code directory to match the project directory and follow the PEP naming conventions for the package.src/pypackitup/__init__.py: Update the package__init__.pywith available imports.src/pypackitup/*.py: Add package code.tests/: Add tests for package code.
Metadata
Release files for pypackitup 1.0.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 |
|---|---|---|---|---|
| pypackitup-1.0.1.tar.gz | 3.0 MB | Without provenance | Details for pypackitup-1.0.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pypackitup-1.0.1-py3-none-any.whl | Python 3 | none | any | Details for pypackitup-1.0.1-py3-none-any.whl |
Total release size: 3.0 MB
Release files / pypackitup-1.0.1.tar.gz
| Download URL | pypackitup-1.0.1.tar.gz |
|---|---|
| Size | 3.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1db12f97f1f357e6f478cd96db7a14400b8727ee6f2d72d8c50e92d272876f18
|
|
BLAKE2b-256 checksum How to use checksums |
6f3ef5651ed73f7268648f7eea98a6f331882b87cca41831650ffd8b9dc1bacb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.5
|
Release files / pypackitup-1.0.1-py3-none-any.whl
| Download URL | pypackitup-1.0.1-py3-none-any.whl |
|---|---|
| Size | 4.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
9df4806c3f7d5e5d072ace41473b27e336ce6b157df64d3b95236e414a3079a6
|
|
BLAKE2b-256 checksum How to use checksums |
79ceb98cfc9c10681a89930acfcb43a668784a2bfdd810d50d0698b2a4ad1a44
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.5.5
|
Security for pypackitup 1.0.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.