Metadata-Version: 2.4
Name: pyplz
Version: 0.12.2
Summary: A Python-first command runner
Project-URL: homepage, https://example.com
Project-URL: repository, https://github.com/yourusername/plz
Requires-Python: >=3.9
Description-Content-Type: text/markdown
Requires-Dist: rich<14,>=13.9.4
Requires-Dist: python-dotenv<2,>=1.0.1

#  <img src="docs/assets/please.png" alt="drawing" width="40" height="40"/> pyplz

Python-first Friction-free Task Runner.

⚠️ Please note ⚠️

`pyplz` is currently in early development. While it is already usable, some features are still missing, incomplete or not fully documented. Feel free to open an issue if you have any feedback or suggestions.

[//]: # (bages using https://shields.io/badges/)
[![build](https://img.shields.io/github/actions/workflow/status/oribarilan/plz/package_build.yml)](https://github.com/oribarilan/plz/actions/workflows/package_build.yml) [![coverage](https://img.shields.io/github/actions/workflow/status/oribarilan/plz/coverage.yml?label=coverage%3E95%25)](https://github.com/oribarilan/plz/actions/workflows/coverage.yml)

[![Python Versions](https://img.shields.io/badge/python-3.8|3.9|3.10|3.11|3.12-blue)](https://www.python.org/downloads/) [![PyPI - Version](https://img.shields.io/pypi/v/pyplz?color=1E7FBF)](https://pypi.org/project/pyplz/) [![Downloads](https://img.shields.io/pypi/dm/pyplz?color=1E7FBF)](https://pypi.org/project/pyplz/)

[![Ruff](https://img.shields.io/endpoint?url=https://raw.githubusercontent.com/astral-sh/ruff/main/assets/badge/v2.json)](https://github.com/astral-sh/ruff)

```bash
pip install pyplz
```

## Why use a task runner?
A task runner automates tasks like building, testing, and deploying, making them
faster and more reliable. It ensures consistent execution and simplifies collaboration
 by providing clear, reusable commands.

## Why `pyplz`?

`pyplz` aims to be a friction-free task runner. While many task runners simplify development, they can also add friction with unfamiliar syntax, extra tools, or difficult integrations.

🐍 **Python-first**: Leverage familiar Python syntax—if you know Python, you know `pyplz`.  

🤗 **Author-friendly**: Intuitive and ready to use out of the box, with built-in support for development & debugging.  

💻 **CLI-compliant**: Enjoy a command-line interface that adheres to GNU and POSIX conventions, ensuring a seamless terminal experience.

🔗 **Integration-ready**: Whether you're running Python locally, in containers, or in a CI/CD pipeline, `pyplz` fits seamlessly into your environment.  

📚 **Documented**: Access extensive documentation and automatically generated task-specific help, ensuring you always have the information you need.

## Getting Started

### Installation
1. Using python 3.9 or later, run `pip install pyplz`
2. Create a `plzfile.py` in the root of your project
3. Using your terminal, execute `plz` in the root of your project

!!! tip "Development Dependencies"
    For best practice, include development dependencies (e.g., `pytest`) in a dedicated file (such as `requirements.dev.txt`). Add `pyplz` to your dev dependencies to ensure it's available out of the box for every project contributor.

### Quick Start

Create your first task by making a `plzfile.py` in your project root:

```python
from pyplz import plz

@plz.task()
def test():
    """Test the project."""
    plz.run("pytest")
```

To add options for test unit tests only (e.g., without integration tests), or adding test coverage, update your task as follows:

```python
from pyplz import plz

@plz.task()
def test(unit_only: bool = False, coverage: bool = False):
    """Test the project."""
    marks = "-m unit" if unit_only else ""
    cov = "--cov" if coverage else ""
    plz.run(f"pytest {marks} {cov}")
```

You can view task-specific help with:
```bash
❯ plz test -h
usage: plz [-h] [--unit-only] [--coverage]

Test the project.

system options:
  -h, --help   Show this help message and exit.

optional arguments:
  --unit-only  Set unit_only to True (bool, default: false)
  --coverage   Set coverage to True (bool, default: false)
```

Now, your `test` task can continue to evolve, without needing some special documentation in a separate file, or a slack message to update your team members!

Read through our documentation to learn how you can use environment variables, define task dependencies and much more!
