Registry / devops / paver
library1.3.4pypypi✓ verified 84d ago

Paver is a Python-based build and task management system, designed to simplify scripting for development, distribution, and deployment. Its last stable release, 1.3.4, was in 2017. The project appears to be unmaintained and is not recommended for new development.

pip install paver
INSTALL
IMPORT
SIG · PAVER
P
paver
devopspythonv1.3.4
Install
1.7s avg
Import
96ms
Disk
18MB
Pass rate
10/ 10
Env Coverage10 / 10
glibc
3.93.13
musl
3.93.13
Install & Compatibility
Where this runs
tested against v1.3.4 · pip install
no network on importno background threads
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
py 3.103.910 runs
installs and imports cleanly · install 0.0s · import 0.098s · 19.6MB
glibc
py 3.103.910 runs
installs and imports cleanly · install 1.7s · import 0.093s · 20MB
18MB installed
● package 18MB
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

*
from paver.easy import *
Paver tasks and utilities are typically imported using 'from paver.easy import *' to make decorators like '@task' and functions like 'path()' directly available.

This quickstart demonstrates defining simple tasks using the '@task' decorator and managing task dependencies with '@needs'. Save the code as `pavement.py` in your project root and run `paver <task_name>` from your terminal.

from paver.easy import * @task def hello(): print("Hello from Paver!") @task @needs('hello') def world(): print("World! This task depends on 'hello'.") # To run: # Save this as 'pavement.py' # Then execute in terminal: 'paver hello' or 'paver world'
paver --version
Debug
Known issues
breakingThe Paver project is no longer actively maintained. Its last release was in 2017, and there have been no significant updates since. Using it for new projects is strongly discouraged.
fix
For new projects, consider modern alternatives like 'invoke', 'poetry', 'flit', or `setuptools` based scripting. For existing projects, be aware of potential compatibility issues with newer Python versions or libraries.
affects: All versions
gotchaWhile Paver 1.3.4 aims for Python 3 compatibility, complex setups, especially those relying on older `distutils` or `setuptools` integrations, may encounter unexpected behavior or errors on newer Python 3 versions.
fix
Thoroughly test existing Paver setups when migrating to newer Python 3 versions. Be prepared to refactor problematic parts or consider migrating to a more actively maintained build system.
affects: 1.x
gotchaPaver's dependency management for tasks, using `@needs`, defines a strict ordering. Misunderstanding how dependencies are resolved can lead to tasks not running in the expected sequence or skipped entirely.
fix
Always explicitly define dependencies using `@needs('task_name')`. For complex graphs, trace the execution path or use a debugger to ensure tasks are invoked as intended. Avoid circular dependencies.
affects: 1.x
Errors
Common errors & fixes
ImportError: No module named paver
The Paver library is not installed in the current Python environment.
fix
Run `pip install paver` to install the library.
NameError: name 'task' is not defined
The '@task' decorator (and other Paver utilities) were not correctly imported.
fix
Ensure `from paver.easy import *` is present at the top of your `pavement.py` file.
No such task: <task_name>
The task specified on the command line does not exist or is misspelled in the `pavement.py` file.
fix
Double-check the task name provided to `paver <task_name>` against the `@task` definitions in `pavement.py`. Ensure the task function is correctly decorated.
Upgrade
Version history
1.3.4latest on PyPI · released Dec 31, 2017
Audit
Dependencies
setuptoolsrequiredRequired for package building and distribution tasks.
Agent activity
4 hits · last 30 days
node
4
Resources
paver — pip install paver · libregistry