emcd-projects
🛠️ Administration utilities for managing projects built from the emcd/python-project-common Copier template.
Installation 📦
Method: Install Executable Script
Install via the uv tool command:
uv tool install emcd-projects
or, run directly with uvx:
uvx --from emcd-projects emcdproj
Or, install via pipx:
pipx install emcd-projects
Method: Install Python Package
Install via uv pip command:
uv pip install emcd-projects
Or, install via pip:
pip install emcd-projects
Features
- 🌐 Static Website Maintenance
Generates badges/shields based on test coverage.
Maintains index of versioned documentation and coverage reports.
No need for Codecov, ReadTheDocs, etc…; static site can be hosted anywhere which can deploy from a Git repo branch (GitHub Pages, etc…).
More Flair
Architecture
The emcdproj package provides maintenance tooling for projects generated from the python-project-common Copier template. It is one component of a larger repository that also contains the template itself, reusable GitHub Actions workflows, and shared documentation.
Package Modules
emcdproj/ ├── __/ # Centralized import hub │ ├── __init__.py # Re-exports core utilities │ ├── imports.py # External library imports │ └── nomina.py # emcd-projects-specific naming constants ├── __init__.py # Package entry point and version ├── __main__.py # CLI entry point for `python -m emcdproj` ├── cli.py # Command-line interface implementation ├── exceptions.py # Package exception hierarchy ├── filesystem.py # File system operations ├── interfaces.py # Common interface definitions ├── website.py # Static website generation and maintenance └── _typedecls/ # Type declaration stubs
Modules generally use the standard __ import pattern for external dependencies, with exceptions for entry points (__main__.py) and subsystems with direct import requirements.
Key Subsystem Contracts
Static Site Publisher (website.py)
Generates and maintains a static documentation site with versioned content, coverage badges, and stable/development aliases. Invoked by the release workflow after documentation and coverage artifacts are available.
Integration with Reusable Workflows
The xrepo--documenter workflow invokes emcdproj website update as part of documentation publication. The xrepo--reporter workflow produces coverage artifacts consumed by the site publisher.
1 maintainer
Metadata
1 maintainer
Release files for emcd-projects 1.62.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 | |
|---|---|---|---|
| emcd_projects-1.62.1.tar.gz | 27.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| emcd_projects-1.62.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.6 kB
Release files / emcd_projects-1.62.1.tar.gz
| Download URL | emcd_projects-1.62.1.tar.gz |
|---|---|
| Size | 27.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
48f322556ba74a057fda2471aa802855447834e8ce901592045968a2116ce47e
|
|
BLAKE2b-256 checksum How to use checksums |
159346e8b05dcc2a81607c96597176cf523d547964b99df019236e78c5674a27
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency logRelease files / emcd_projects-1.62.1-py3-none-any.whl
| Download URL | emcd_projects-1.62.1-py3-none-any.whl |
|---|---|
| Size | 40.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66400d87f4b9d0e1bb2d12f0bdb452dea548340009d7dc0974266430f7f25f4a
|
|
BLAKE2b-256 checksum How to use checksums |
1defeb49fd39fbfb737918aae871b06ced3fd72bc6aaaff57510788039e62cf6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 14, 2026.
Transparency log
