the work sandbox.

* Updated svn externals to include Zope 3.2 (currently the Zope3 trunk);
  that includes two new top-level packages, pytz and zodbcode, as well as
  the following new zope.* packages:
  - zope.deprecation
  - zope.dottedname
  - zope.formlib
  - zope.index
  - zope.testbrowser

* Moved to a zpkgutils-based build system, as the Zope 3.2 extension modules
  require to be built with it. If everything goes ahead as planned, the release
  tarball will also be built with zpkgutils (some work has also been done in
  that direction).

* Upgraded Five to the 1.3b release (released today) which is a Zope 3.2-compatible
  version of Five 1.2b (also released today). Biggest implication of this on the
  Zope 2 trunk is that the event work by Florent Guillaume has been folded back
  into the Zope 2 core, i.e. the OFS package.

* A few fixes to the Zope 2 PageTemplate/TAL/TALES implementation to work with the
  new immutable i18n Messages available since Zope 3.1+ (and standard in Zope 3.2).

Event interfaces are now in OFS.interfaces.
IFiveObjectClonedEvent has been renamed into IObjectClonedEvent.

i18n Messages. Made DummyEngine work with them.

going to include in Zope 2 (yet?).

but I really want this fix...):

  Incorporated test runner bug fixes:
  
  - --verbose --progress didn't do what people expected
  
  - --module matched module file paths rather than module dotted names
  
  - Positional arguments weren't handled correctly
  
  Changed the test-runner script, test.py to exclude packages currently
  gotten via externals.

something in the error_log.

- --verbose --progress didn't do what people expected

- --module matched module file paths rather than module dotted names

- Positional arguments weren't handled correctly

Changed the test-runner script, test.py to exclude packages currently
gotten via externals.

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

- import and whitespace cleanup

Doing so wipes out all the warning filters other tests may set
up to suppress warnings those tests need to provoke but want to
hide from the entity running the tests.

This stops all the DeprecationWarnings that were displayed from
the ZODB and ZEO tests when running Zope trunk's test suite.