poe-tasks-common
An opinionated collection of common poe tasks
About
The poe task runner allows developers to create commands that run repeated tasks for software development. Common examples include commands for formatting the code, running the tests, and building the documentation. The poe-tasks-common package provides a pre-configured collection of these tasks. By adding poe-tasks-common to your pyproject.toml file, you gain immediate access to core environment, security, linting, testing, and documentation commands, without needing to learn to build poe tasks.
Examples
By adding poe-tasks-common to a pyproject.toml file, you gain immediate access to commands like:
# Checks for security vulnerabilities
poe audit
# Formats the code and tests
poe format
# Lints the code and tests
poe lint
# Runs the tests, requires a certain coverage.
# Opens coverage report in a web browser.
poe tests
poe htmlcov
# Builds the docs. Opens docs in a web browser
poe docs
poe open-docs
Opinionated Toolset
As stated, poe-tasks-common is an opinionated collection - the tasks it provides are intended for specific developer tools like pytest, ruff, pip-audit and others. We are not claiming that these tools are the absolute best choices for every possible use case. Rather, this toolset is intended as a common core suitable for many projects. We also emphasize that poe-tasks-common provides options for filtering out unwanted tools and tasks.
When to use poe-tasks-common
Use poe-tasks-common when you want to quickly start developing a project, without needing to configure poe commands. The package is also useful when you want a common core of commands that you can use across multiple projects. Finally, advanced users may find the package a useful building block for more complex poe frameworks.
Metadata
Release files for poe-tasks-common 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 | |
|---|---|---|---|---|
| poe_tasks_common-0.2.0.tar.gz | 6.9 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| poe_tasks_common-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 16.6 kB
Release files / poe_tasks_common-0.2.0.tar.gz
| Download URL | poe_tasks_common-0.2.0.tar.gz |
|---|---|
| Size | 6.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
eab5c06bc443b9ce9257608e7d9630fa59176957b1b2a41325c59a5ac9cbab5c
|
|
BLAKE2b-256 checksum How to use checksums |
3aeed2f5238e71f00e67bc4feb61f8408cdbb802cae1c49f8ba5f624097c1b36
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / poe_tasks_common-0.2.0-py3-none-any.whl
| Download URL | poe_tasks_common-0.2.0-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
43743aa9af4addb9ee4448feba545d9fe02cf47ed98411b0e2502b6074bfa883
|
|
BLAKE2b-256 checksum How to use checksums |
b656a1dbff72c995985022c89e5373ccfdf2bbc11ebbbb536ba34cb3cc27e1e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.13.1 {"installer":{"name":"uv","version":"0.13.1","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for poe-tasks-common 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.
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.