Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Kevin Dangoor <dangoor <at> gmail.com>
Subject: Paver 1.0 released
Newsgroups: gmane.comp.python.announce
Date: Monday 23rd March 2009 01:55:04 UTC (over 7 years ago)
After months of use in production and about two months of public testing
for
1.0, Paver 1.0 has been released. The changes between Paver 0.8.1, the most
recent stable release, and 1.0 are quite significant. Paver 1.0 is easier,
cleaner, less magical and just better all around. The backwards
compatibility breaks should be easy enough to work around, are described in
DeprecationWarnings and were introduced in 1.0a1 back in January.
Paver's home page: http://www.blueskyonmars.com/projects/paver/

What is Paver?
===========

Paver is a Python-based software project scripting tool along the
lines of Make or Rake. It is not designed to handle the dependency
tracking requirements of, for example, a C program. It *is* designed
to help out with all of your other repetitive tasks (run documentation
generators, moving files about, downloading things), all with the
convenience of Python's syntax and massive library of code.

If you're developing applications in Python, you get even more...
Most public Python projects use distutils or setuptools to create source
tarballs for distribution. (Private projects can take advantage of
this, too!) Have you ever wanted to generate the docs before building the
source distribution? With Paver, you can, trivially. Here's a complete
pavement.py::

    from paver.easy import *
    from paver.setuputils import setup

    setup(
        name="MyCoolProject",
        packages=['mycool'],
        version="1.0",
        url="http://www.blueskyonmars.com/",
        author="Kevin Dangoor",
        author_email="[email protected]"
    )

    @task
    @needs(['html', "distutils.command.sdist"])
    def sdist():
        """Generate docs and source distribution."""
        pass

With that pavement file, you can just run ``paver sdist``, and your docs
will be rebuilt automatically before creating the source distribution.
It's also easy to move the generated docs into some other directory
(and, of course, you can tell Paver where your docs are stored,
if they're not in the default location.)

Installation
------------

The easiest way to get Paver is if you have setuptools_ installed.

``easy_install Paver``

Without setuptools, it's still pretty easy. Download the Paver .tgz file
from
`Paver's Cheeseshop page`_, untar it and run:

``python setup.py install``

.. _Paver's Cheeseshop page: http://pypi.python.org/pypi/Paver/
.. _setuptools: http://peak.telecommunity.com/DevCenter/EasyInstall

Help and Development
--------------------

You can get help from the `mailing list`_.

If you'd like to help out with Paver, you can check the code out from
Googlecode:

``svn checkout http://paver.googlecode.com/svn/trunk/
paver-read-only``

You can also take a look at `Paver's project page on Googlecode <
http://code.google.com/p/paver/>`_.

.. _mailing list: http://groups.google.com/group/paver


-- 
Kevin Dangoor

work: http://labs.mozilla.com/
email: [email protected]
blog: http://www.BlueSkyOnMars.com
 
CD: 4ms