[Zodb-checkins] CVS: Zope3/src/ZConfig - NEWS.txt:1.1 PACKAGE.cfg:1.1 README.txt:1.1 INSTALL.cfg:1.3

Fred L. Drake, Jr. fred at zope.com
Mon Apr 19 12:12:13 EDT 2004

Update of /cvs-repository/Zope3/src/ZConfig
In directory cvs.zope.org:/tmp/cvs-serv11244

Modified Files:
Added Files:
Log Message:
add the files necessary to create a distribution directly from the ZConfig
package using zpkg; this creates a normal end-user accessible distribution

=== Added File Zope3/src/ZConfig/NEWS.txt ===
Changes since ZConfig 2.1:

- More documentation has been written.

- Added a timedelta datatype function; the input is the same as for
  the time-interval datatype, but the resulting value is a
  datetime.timedelta object.

- Make sure keys specified as attributes of the <default> element are
  converted by the appropriate key type, and are re-checked for
  derived sections.

- Refactored the ZConfig.components.logger schema components so that a
  schema can import just one of the "eventlog" or "logger" sections if
  desired.  This can be helpful to avoid naming conflicts.

- Added a reopen() method to the logger factories.

- Always use an absolute pathname when opening a FileHandler.

Changes since ZConfig 2.0:

- Removed compatibility with Python 2.1 and 2.2.

- Schema components must really be in Python packages; the directory
  search has been modified to perform an import to locate the package
  rather than incorrectly implementing the search algorithm.

- The default objects use for section values now provide a method
  getSectionAttributes(); this returns a list of all the attributes of
  the section object which store configuration-defined data (including
  information derived from the schema).

- Default information can now be included in a schema for <key
  name="+"> and <multikey name="+"> by using <default key="...">.

- More documentation has been added to discuss schema extension.

- Support for a Unicode-free Python has been fixed.

- Derived section types now inherit the datatype of the base type if
  no datatype is identified explicitly.

- Derived section types can now override the keytype instead of always
  inheriting from their base type.

- <import package='...'/> makes use of the current prefix if the
  package name begins witha dot.

- Added two standard datatypes:  dotted-name and dotted-suffix.

- Added two standard schema components: ZConfig.components.basic and

Changes since ZConfig 1.0:

- Configurations can import additional schema components using a new
  "%import" directive; this can be used to integrate 3rd-party
  components into an application.

- Schemas may be extended using a new "extends" attribute on the
  <schema> element.

- Better error messages when elements in a schema definition are
  improperly nested.

- The "zconfig" script can now simply verify that a schema definition
  is valid, if that's all that's needed.

=== Added File Zope3/src/ZConfig/PACKAGE.cfg ===
# Add a few things to the top of the distribution.

  doc          doc
  LICENSE.txt  http://cvs.zope.org/Zope3/ZopePublicLicense.txt?rev=HEAD
  NEWS.txt     NEWS.txt
  README.txt   README.txt

# and remove the same from the package itself.
  doc          -
  NEWS.txt     -
  README.txt   -

  # We'll remove this too, since it's only of interest to CVS users:
  BRANCHES.txt -

=== Added File Zope3/src/ZConfig/README.txt ===
This is ZConfig.

ZConfig is a configuration library intended for general use.  It
supports a hierarchical schema-driven configuration model that allows
a schema to specify data conversion routines written in Python.
ZConfig's model is very different from the model supported by the
ConfigParser module found in Python's standard library, and is more
suitable to configuration-intensive applications.

ZConfig schema are written in an XML-based language and are able to
"import" schema components provided by Python packages.  Since
components are able to bind to conversion functions provided by Python
code in the package (or elsewhere), configuration objects can be
arbitrarily complex, with values that have been verified against
arbitrary constraints.  This makes it easy for applications to
separate configuration support from configuration loading even with
configuration data being defined and consumed by a wide range of
separate packages.

ZConfig is licensed under the Zope Public License, version 2.0.  See
the file LICENSE.txt in the distribution for the full license text.

Reference documentation is available in the ZConfig/doc/ directory.

Information on the latest released version of the ZConfig package is
available at


You may either create an RPM and install this, or install directly from
the source distribution.

Creating RPMS:

  python setup.py bdist_rpm

  If you need to force the Python interpreter to, for example, python2:

    python2 setup.py bdist_rpm --python=python2

Installation from the source distribution:

    python setup.py install

  To install to a user's home-dir:
    python setup.py install --home=<dir>

  To install to another prefix (eg. /usr/local)
    python setup.py install --prefix=/usr/local

  If you need to force the python interpreter to eg. python2:
    python2 setup.py install

  For more information please refer to

=== Zope3/src/ZConfig/INSTALL.cfg 1.2 => 1.3 ===
--- Zope3/src/ZConfig/INSTALL.cfg:1.2	Mon Apr 12 11:31:02 2004
+++ Zope3/src/ZConfig/INSTALL.cfg	Mon Apr 19 12:12:12 2004
@@ -1,6 +1,6 @@
 # Metadata used by zpkg (mostly a sample for testing).
-documentation  doc/zconfig.pdf
-documentation  doc/schema.dtd
+#documentation  doc/zconfig.pdf
+#documentation  doc/schema.dtd
 script scripts/zconfig*

More information about the Zodb-checkins mailing list