As 'setuptools' is a dependency 'pkg_resources' will be available always. Ref: http://mail.zope.org/pipermail/zope-dev/2009-March/035277.html

  on ``zope.exceptions``:

  o ``zope.exceptions.DuplicationError`` -> ``KeyError``

  o ``zope.exceptions.UserError`` -> ``ValueError``

 
 o That package has no dependencies beyond ``zope.interface``.
 
Made ``test`` part pull in the extra test requirements of this package.

Split the ``z3c.recipe.compattest`` configuration out into a new file,

 o New file, ``compat.cfg``, allows doing the full compatibility testing
   without adding the extra dependencies while doing standard unit tests.

Stripped out bogus develop eggs from ``buildout.cfg``.

The content-type declaration belongs to zope.app.folder, not zope.container. This came in here accidentally.

now, while it didn't seem before. testing against all trunks must've
somehow shuffled dependencies around.

dependency which should've been declared already.

now as zope.app.component needs it, and we still need that).

re-added include directory (headers can't be reached from distributed eggs), externals are the best solution currently