Skip to main content

Python project quick scripts

Project description

Python project quick scripts

Define simple project management scripts in pyproject.toml

Developing a Python project usually involves many tasks: setting up, installing prerequisites, building, testing, cleaning up build products, etc. It can be difficult to remember which program to run to perform a given task for a given project, particularly when many different tools are being used.

ppqs defines simple ("quick") scripts in pyproject.toml, and provides a command-line utility -- ppqs -- to run them. In this way ppqs hides the details of whatever dependency/virtual environment manager, build front-end, test harness, etc. the project uses behind a simple interface.

Here is an example of ppqs being used for its own project:

$ ppqs --help
Quick scripts for Python project: ppqs

Usage: ppqs {init,lint,build,test,clean}

Scripts:
  init   Initialise project
  lint   Perform linting checks
  build  Build project
  test   Run tests
  clean  Clean up build files

Scripts are always run from the project root directory, i.e. the directory containing pyproject.toml. ppqs traverses back through parent directories until it finds the root directory. It is therefore safe to run ppqs from any sub-directory within the project directory tree.

Script definition in pyproject.toml

ppqs scripts are simple lists of commands which are run in sequence. If a command errors, the remainder of the script is aborted.

Scripts are defined in pyproject.toml under the [tool.ppqs.scripts] section. Script names may contain only lowercase letters ([a-z]) and dashes (-). Scripts may be single or multi-line strings: commands are separated by newlines, and command arguments are separated by spaces.

[tool.ppqs.scripts]
init = "command"
lint = """
command
"""
build = """
command1 -v
command2 -q
"""

Scripts may also be defined as lists of lists, i.e. a list of commands, each of which is a list of arguments:

[tool.ppqs.scripts]
test = [
    ["command1"],
    ["command2", "-vv"],
]
clean = [
    ["command"],
]

If a script contains an ellipsis (...) it is replaced with any additional arguments passed to ppqs. For example, the following script:

[tool.ppqs.scripts]
print-something = "echo ..."

may be run as

$ ppqs print-something Hi
Hi

The following only applies to scripts defined as lists of lists: if a command argument is itself a list, it is concatenated into a path appropriate for the current operating system. For example,

[tool.ppqs.scripts]
do-something = [["do-something-to", ["subdir", "afile"]]]

would run the command do-something-to subdir/afile on a Unix-based operating system.

Scripts may also be defined in their own section, which permit a few options:

[tool.ppqs.scripts.init]
description = "Initialise project"
print-header = true
script = """
command
"""

[tool.ppqs.scripts.build]
script = [
    ["command1", "-v"],
    ["command2", "-q"],
]

where:

  • description (optional): description of the script which appears in ppqs --help. Default is Run {name} script where name is the script name.

  • print-header (optional): If true, print a header before running each command in the script. The header consists of the command to be run, centred on the console and padded with *s. Default is false.

The default value of some options may be overridden in the [tool.ppqs.defaults] section, e.g.

[tool.ppqs.defaults]
print-header = true

Note that commands are not passed to the shell, so shell features (e.g. wildcards, conditional statements) are not available. The recommended solution is to write a helper script, e.g. scripts/lots-to-do.py, which may then be called by ppqs as:

[tool.ppqs.scripts]
lots-to-do = [["python", "scripts/lots-to-do.py"]]

Bash completion

ppqs support Bash command-line completion. Simply add the following command to your ~/.bashrc file:

complete -C "ppqs --bash-completion" ppqs

Typing ppqs and hitting TAB will then show scripts available for the current project. Typing part of a script name and hitting TAB will show matching script name(s), or else complete the full name if unambiguous.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

ppqs-2.0.1.tar.gz (7.9 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

ppqs-2.0.1-py3-none-any.whl (6.7 kB view details)

Uploaded Python 3

File details

Details for the file ppqs-2.0.1.tar.gz.

File metadata

  • Download URL: ppqs-2.0.1.tar.gz
  • Upload date:
  • Size: 7.9 kB
  • Tags: Source
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.10.12

File hashes

Hashes for ppqs-2.0.1.tar.gz
Algorithm Hash digest
SHA256 b00fcbac191d955718a5d25be62aa1bb236efbd7a176a651563d3574b36c9ba5
MD5 5de3ddc6183985c161cba95eb3bc250c
BLAKE2b-256 167cb5abd1339f12ea54f5f876fe2f9bbfc5824d7163403e328cc5fabcfb5f33

See more details on using hashes here.

File details

Details for the file ppqs-2.0.1-py3-none-any.whl.

File metadata

  • Download URL: ppqs-2.0.1-py3-none-any.whl
  • Upload date:
  • Size: 6.7 kB
  • Tags: Python 3
  • Uploaded using Trusted Publishing? No
  • Uploaded via: twine/6.1.0 CPython/3.10.12

File hashes

Hashes for ppqs-2.0.1-py3-none-any.whl
Algorithm Hash digest
SHA256 91f334aebe693998fe2deb37d3ff7517a06d0e7215d3e8fe2c3d93f9a6dd893a
MD5 134282996a0719862196a632e2509a8f
BLAKE2b-256 e26d2393c9ed6a830f567ccc60662c30ac7ec5c7c6ce06d158c647b3e0f87b59

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page