I’ve just released Paver 1.0b1. This new release adds a fun little feature. A typical setup.py script looks like this:
from distutils.core import setup setup(name="Foo", ...)
With the new version of Paver, you can now rename setup.py to pavement.py (or run
paver -f setup.py) and then do:
from paver.setuputils import setup setup(name="Foo", ...)
That gets you going quite quickly, doesn’t it? Of course, you’d likely want to add
from paver.easy import * and to start making tasks that take advantage of Paver.
1.0b1 includes some other bug fixes, brings back the call_task function (particularly useful for distutils tasks), and makes the help output more consistent.
There’s one more bug on my list to fix (the distutils output is not showing up), and then I need to rework the docs for Paver 1.0.
Update: It occurred to me a bit later that my example above doesn’t work, because you need to call install_distutils_tasks to get Paver to pick up all of the distutils/setuptools commands. However, this will be fixed in rc1.