the --quiet parameter.

versions were much too verbose by default.

testrunner.py last week.

configuration file template (reflects recent addition of a "products"
key to the template).

When this is done, the makefile and all temp build files are written to
the directory from which you run configure.  This is to support
Tres' desire to be able to install Zope from read-only media.

Perform minor cleanups, extensions, and refactorings of setup.py and
configure.py along the way.

information on tests that fail, regardless of the verbosity setting.
This allows using -v0 or -v1, and still seeing useful error
information as the tests are run.  This is especially helpful for
large or long-running test suites.

from the filesystem.

implementation, to allow the PageTemplateFile class to override what
happens when the check is performed.

the Zope configuration file.  There is no magical search for
INSTANCE_HOME/Products; it is included as part of the instance skeleton,
but can be controlled simply changing the configuration.

it contains have been moved to the Packages/pcgi module in the cvs.zope.org
public CVS repository; it can be distributed as a separate package for those
who need it.

This corresponds to Zope 3 collector issue 129.
http://collector.zope.org/Zope3-dev/129

  underlying database adapter should convert a unicode to the encoding the
  database expects.

"makefile".  This is a little painful, since the names match in everything
but case.  It appears to be impossible to use a generated file with the same
name as a file previously in the repository, even with the help of .cvsignore.

of ZServer.

package.

new-install-branch.

new-install-branch.

try/except so we need to explicitly check.

for Python 2.2.  This avoids a warning that can be issued during the initial
startup.

- don't pretend directories inside packages are themselves packages if
  they aren't; list them using the "data_files" keyword (this avoids
  noisy warnings for installation and out-of-place building)