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.2
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.2.tar.gz | 7.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| minchin_tasks-1.1.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 15.6 kB
Release files / minchin_tasks-1.1.2.tar.gz
| Download URL | minchin_tasks-1.1.2.tar.gz |
|---|---|
| Size | 7.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
8dc5699103acea4b16f1ba50146179d263445d6ffc49c7896ffebce160544e9c
|
|
BLAKE2b-256 checksum How to use checksums |
e58c60d5bf25aed4b44f22c3aea08769e18ec6bb38f9ca50474a36898f2b890d
|
| 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.2-py3-none-any.whl
| Download URL | minchin_tasks-1.1.2-py3-none-any.whl |
|---|---|
| Size | 7.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23487e13479a6e188f859cc414e1ef5afc69e7ea7d97f77da75b8ea297c70ab1
|
|
BLAKE2b-256 checksum How to use checksums |
bb9c6b8c5c84a8db9602b5fb1414c589e9e5196c6387c2439ba5eaaeba0436bf
|
| 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.2
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.
