To find out what’s new in this version of Invoke, please see the changelog.
Invoke is a Python (2.6+ and 3.3+) task execution tool & library, drawing inspiration from various sources to arrive at a powerful & clean feature set.
Like Ruby’s Rake tool and Invoke’s own predecessor Fabric 1.x, it provides a clean, high level API for running shell commands and defining/organizing task functions from a tasks.py file:
from invoke import task @task def clean(ctx, docs=False, bytecode=False, extra=''): patterns = ['build'] if docs: patterns.append('docs/_build') if bytecode: patterns.append('**/*.pyc') if extra: patterns.append(extra) for pattern in patterns: ctx.run("rm -rf %s" % pattern) @task def build(ctx, docs=False): ctx.run("python setup.py build") if docs: ctx.run("sphinx-build docs docs/_build")From GNU Make, it inherits an emphasis on minimal boilerplate for common patterns and the ability to run multiple tasks in a single invocation:
$ invoke clean build
Following the lead of most Unix CLI applications, it offers a traditional flag-based style of command-line parsing, deriving flag names and value types from task signatures (optionally, of course!):
$ invoke clean --docs --bytecode build --docs --extra='**/*.pyo' $ invoke clean -d -b build --docs -e '**/*.pyo' $ invoke clean -db build -de '**/*.pyo'
Like many of its predecessors, it offers advanced features as well – namespacing, task aliasing, before/after hooks, parallel execution and more.
For documentation, including detailed installation information, please see http://pyinvoke.org. Post-install usage information may be found in invoke --help.
You can install the development version via pip install -e git+https://github.com/pyinvoke/invoke#egg=invoke.
Metadata
Release files for invoke 0.14.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 |
|---|---|---|---|---|
| invoke-0.14.0.tar.gz | 247.3 kB | Without provenance | Details for invoke-0.14.0.tar.gz |
Built distributions (wheels)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| invoke-0.14.0-py3-none-any.whl | Python 3 | none | any | Details for invoke-0.14.0-py3-none-any.whl |
| invoke-0.14.0-py2-none-any.whl | Python 2 | none | any | Details for invoke-0.14.0-py2-none-any.whl |
Total release size: 510.9 kB
Release files / invoke-0.14.0.tar.gz
| Download URL | invoke-0.14.0.tar.gz |
|---|---|
| Size | 247.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5daa0882831ab56611b870851a7ad4025152623f83812ff32fd70dbf62fc1bee
|
|
BLAKE2b-256 checksum How to use checksums |
de83a8d5f2fb626bd79c84260be1dd4a05821fa59299bb261131ba07d80c1bf8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / invoke-0.14.0-py3-none-any.whl
| Download URL | invoke-0.14.0-py3-none-any.whl |
|---|---|
| Size | 131.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cac781c81206150d3ba6d23ce2c3ef01cea6872aba06baa025136c926422595d
|
|
BLAKE2b-256 checksum How to use checksums |
16ce63df8915bc373f068b47dd336088c7c0d90ecfdc73ad83aff127fe7b0566
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Release files / invoke-0.14.0-py2-none-any.whl
| Download URL | invoke-0.14.0-py2-none-any.whl |
|---|---|
| Size | 132.2 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
c8e937b8bea2eea5b27320c606371e5a1b8e27d4b2b3eddbd21d3ebb2419939b
|
|
BLAKE2b-256 checksum How to use checksums |
40cae1b2f0fdd451afa56f3c9a32a1c8f1186b1583b164cddd8eb020a5d69bc5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for invoke 0.14.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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.