- Rid ourselves of ``IObjectMovedEvent``, ``IObjectAddedEvent``,
  ``IObjectRemovedEvent`` interfaces and ``ObjectMovedEvent``,
  ``ObjectAddedEvent`` and ``ObjectRemovedEvent`` classes.  All of
  these were moved to ``zope.lifecycleevent``. Depend on
  ``zope.lifecycleevent``>=3.5.2.

  condition on the qsubscriber ZCML directive that registers the
  CheckDependency handler for IObjectRemovedEvent.  If
  ``zope.app.dependable`` is not installed, this subscriber will never
  be registered.  ``zope.app.dependable`` is now a testing dependency
  only.

  zope.traversing.api.getPath in favor of using
  ILocationInfo(object).getPath().  The rest of the runtime
  dependencies on zope.traversing are currently interface
  dependencies.

- added coverage analysis

Fixes: https://bugs.launchpad.net/bugs/348329
(Thanks to Gary Poster for the idea, see r98787)

  ``IOrdered`` interface and let ``IOrderedContainer`` inherit it. This allows
  easier reuse of the declaration.

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.