pytaskwarrior
A modern Python library for TaskWarrior v3.x task management.
No task binary required. pytaskwarrior uses
taskchampion3-py-dev — Rust bindings
to the taskchampion storage engine — for direct, high-performance SQLite access.
Features
- No external binary — reads/writes TaskWarrior's SQLite database directly
- Full CRUD operations — Create, read, update, delete tasks
- Type-safe — Pydantic models with full type hints
- Context management — Define, apply, and switch contexts (reads/writes
.taskrc) - UDA support — User Defined Attributes
- Virtual tags —
+OVERDUE,+DUE,+TODAY,+WEEK,+BLOCKED,+READY, and 20+ more - Date expressions —
due.before:tomorrow,due.after:eom, compound expressions (now + P3D) - Recurring tasks — Full recurrence support
- Annotations — Add notes to tasks
- Sync — Remote and local directory sync via taskchampion protocol
- Optional CLI fallback — Pass
task_cmd="task"to use the classic CLI adapter
Requirements
- Python 3.9+
taskchampion3-py-dev>= 3.0.1.3 (installed automatically)
The task binary is not required for the default adapter.
Installation
pip install pytaskwarrior
Quick Start
from taskwarrior import TaskWarrior, TaskInputDTO, Priority
# No binary needed — uses taskchampion SQLite backend directly
tw = TaskWarrior()
# Create a task
task = tw.add_task(TaskInputDTO(
description="Finish project report",
priority=Priority.HIGH,
project="work",
tags=["urgent"],
due="friday",
))
# Query tasks
for t in tw.get_tasks("project:work +READY"):
print(f"[{t.priority or '-'}] {t.description}")
# Virtual tag filtering
overdue = tw.get_tasks("+OVERDUE")
due_soon = tw.get_tasks("due.before:eow")
# Complete a task
tw.done_task(task.uuid)
Documentation
Full documentation: pytaskwarrior.readthedocs.io
See Also
- TaskMajor — MCP server providing TaskWarrior integration for AI assistants. Built entirely on pytaskwarrior.
1 maintainer
Metadata
1 maintainer
Release files for pytaskwarrior 3.0.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 | |
|---|---|---|---|---|
| pytaskwarrior-3.0.2.tar.gz | 50.0 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| pytaskwarrior-3.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 109.1 kB
Release files / pytaskwarrior-3.0.2.tar.gz
| Download URL | pytaskwarrior-3.0.2.tar.gz |
|---|---|
| Size | 50.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b8a4d7271be29b7ff749563c5240e13314b947b150507a61cf9fb1ebae53e03
|
|
BLAKE2b-256 checksum How to use checksums |
e831cda8b4ee14c1cb00e5efd5ff42a3d96b9e28c4de3e04fbd70d49ac4cf9c2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logRelease files / pytaskwarrior-3.0.2-py3-none-any.whl
| Download URL | pytaskwarrior-3.0.2-py3-none-any.whl |
|---|---|
| Size | 59.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b50ad16f4ef7be69eeffc9e9d7ae4c802d1e28e599dea430c2593831b4b7545b
|
|
BLAKE2b-256 checksum How to use checksums |
ad8dfbcfa33aa4d8dad0356b18bdf2652a9cdf26ee90b59540cf54da7f13f2e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logSecurity for pytaskwarrior 3.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pytaskwarrior-3.0.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 23, 2026.
Transparency logA 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.
