Minchin.Tasks
Common development tasks for use with Invoke. Defaults to a uv and ruff setup, but should continue to work with black, isort, and pip-tools. Useful for applying my in-house Python style, see https://github.com/minchinweb/python-style-guide
In your tasks.py (import each for clarity):
from minchin.tasks import check, format_code, lint, test, update, upgrade # noqa: F401 from minchin.tasks import pelican_build # noqa: F401
This gives you:
invoke update – update requirements to the current versions
invoke upgrade – install the locked requirements
invoke lint – report only format check, including pyproject.toml
invoke format – fix formatting issues
invoke test – run pytest.
invoke check – lint and test.
invoke pelican-build – build the local Pelican site
1 maintainer
Metadata
1 maintainer
Release files for minchin.tasks 1.1.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 | |
|---|---|---|---|---|
| minchin_tasks-1.1.0.tar.gz | 7.4 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| minchin_tasks-1.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 14.5 kB
Release files / minchin_tasks-1.1.0.tar.gz
| Download URL | minchin_tasks-1.1.0.tar.gz |
|---|---|
| Size | 7.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7218ac10a19a4d1ee52ab6b6782701ee15699b81948763d61c72ee241ec8d138
|
|
BLAKE2b-256 checksum How to use checksums |
2d2dd76d3400d0d3b08e58934dd4e69f2a614d7104ffe8bd5556ec9a0e735359
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.12
|
Release files / minchin_tasks-1.1.0-py3-none-any.whl
| Download URL | minchin_tasks-1.1.0-py3-none-any.whl |
|---|---|
| Size | 7.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f66c4c09e9a9fa4d881178b598987f4aa0869312d05bd12e7b3f3ebdf10f5a07
|
|
BLAKE2b-256 checksum How to use checksums |
57d904599c54439d01ff9c7fc866195c03f18cf922b2e5dff81f6d06d2b1b352
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/7.0.0 CPython/3.12.12
|
Security for minchin.tasks 1.1.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.
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.
