they assume the application object it the standard one which includes an
error_log. But run in isolation they would pass.

Now we make sure an error_log is present in the application object.

- mark a test class as deprecated,
- use a container class that implements IItem.

doesn't have support for that. yet.

somebody might readd this, as a version that is rewritten for Zope 2.

also removed duplicate entry on docutils

get rid of links to files that aren't in Zope 2

standard containers. manage_afterAdd, manage_beforeDelete and
manage_afterClone are now deprecated. See
lib/python/Products/Five/tests/event.txt for details.

This requires Five 1.3 (included in Zope 2.9).

Zope2-src is a virtual collection, located at releases/Zope2/ and defines
what goes into a Zope 2 release tarball.

directory, overwriting the stub I copied from Zope 3.

(the Zope 2 makefile does way too much...)

And ... WOW. it works! Yay.

proves my little knowledge of zpkgutils.

though, so it doesn't work yet.

to reset the site thread local variable; otherwise local sites would be
carried across browser requests which wouldn't be desirable

be bootstrapped which in turn are needed for Zope 3 style translation.
Zope 3.2 has the a global utility registry available at all times, though.

all the time)

Stops deprecation warnings from ZODB 3.6.

Still no idea why deprecation warnings from the ZODB tests
show up (ZODB is already trying to suppress them, and that
works fine in a ZODB checkout and in a Zope3 checkout).

Make sure that savepoint creation is optimistic.

Also, now tests will be searched for in lib/python of instances.

No commit message

The checkin implies:

  - the "DBTab" package has been removed.  It is no longer necessary.
    Instead, we use ZODB 3.6's built-in multidatabase support.

  - ZODBMountPoint no longer monkey-patches ZODB to allow for mount
    support.

  - We temporarily hack setup.py to allow ZODB 3.6.0b1 to be compiled
    (it expects to be compiled via ZPackage).