pyrepo-init
pyrepo-init is a reusable Python repository starter with packaging, tests,
linting, documentation, and PyPI publishing configuration already wired in.
Use it as a starting point for small Python packages that should be installable
with pip, testable with pytest, and releasable through GitHub Actions.
Installation
pip install pyrepo-init
Usage
from pyrepo_init.main import get_message
print(get_message())
Or via command line:
pyrepo-init
python -m pyrepo_init
Development
python -m pip install --upgrade pip nox
nox -s test
nox -s lint
nox -s docs
Release to PyPI
Before publishing, verify that the package builds cleanly:
python -m pip install --upgrade build twine
python -m build
python -m twine check dist/*
This repository includes .github/workflows/publish-pypi.yml:
- Manual
workflow_dispatchpublishes to TestPyPI. - Publishing a GitHub release publishes to PyPI.
Configure trusted publishing for shenxianpeng/pyrepo-init on PyPI and
TestPyPI before releasing.
License
MIT
Metadata
Release files for pyrepo-init 0.2.0
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 |
|---|---|---|---|---|
| pyrepo_init-0.2.0.tar.gz | 7.2 kB | With provenance | Details for pyrepo_init-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pyrepo_init-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for pyrepo_init-0.2.0-py3-none-any.whl |
Total release size: 11.2 kB
Release files / pyrepo_init-0.2.0.tar.gz
| Download URL | pyrepo_init-0.2.0.tar.gz |
|---|---|
| Size | 7.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0904abdda76bc8cccd46cc7dcbc867c9317ef5ce5b245acfd615cd70df69f3e1
|
|
BLAKE2b-256 checksum How to use checksums |
c642adc77fcc7593ad0baf95ab8ec7b7aa6ab0999c69309ad88c5e57e7dc4996
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 17, 2026.
Transparency logRelease files / pyrepo_init-0.2.0-py3-none-any.whl
| Download URL | pyrepo_init-0.2.0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de8a14bb7bbbc090abcebff82328d67827c077308c2512d7ca2dcecdeda271f2
|
|
BLAKE2b-256 checksum How to use checksums |
e87b309a83c184bdf901d5d46ae9e106abbea11e004beb890113e052a48d7e7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 May 17, 2026.
Transparency logSecurity for pyrepo-init 0.2.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for pyrepo_init-0.2.0.tar.gz
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 May 17, 2026.
Transparency logA 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.