- made sure custom strings like MessageID are not converted by ustr
- synced TALInterpreter code and tests with zope.tal where possible without changing behavior
- backported MessageID support from zope.tal

See the thread starting at
 http://mail.zope.org/pipermail/zope/2005-July/160433.html
for gory details.

Note that Zope trunk and 2.8 also have a third copy of this
code, in

    lib/python/zope/server/trigger.py

That's "a Zope3 problem".

      - Collector #1807: fixed memory leak in cAccessControl.guarded_getattr()

Additional test. CMF requires this behaviour.

Display offending line when warning about getOwner(1) deprecation.

Will stitch in again via svn:externals.

(http://www.zope.org/Collectors/Zope/1813).

o CMFCore will include it after 1.5, with an appropriate module alias for
  backward compatibility.

This also includes a patch to HTTPRequest which is implemented
directly in Zope 2 rather than the monkey Five does.

 collector 1828 which was already marked as resolved.

(this fixes the infinite loop issue, but adds redundant interface definitions because we can't use Five's bridging code)

- Collector #1815: ZCTextIndex accepts (again) sequences of strings to be indexed.

      - Collector #1812: Fixed key error in ZSQL ZMI/Test

- Forward-port fix from 2.7:

      - WebDAV COPY and MOVE did not call '_notifyOfCopyTo' and
        '_postCopy' hooks like it was done in
        OFS.CopySupport. Additionally added
        'manage_changeOwnershipType' to make MOVE behave even closer
        to OFS.CopySupport.

Shut down cleanly when Windows is shutting down.

The caller can't deal with using current data from loadBefore, so having an "end_tid" of None is useless.

No commit message

Allow tempstorage to participate in MVCC.  Also fix minor bug where conflict cache could be poisoned by a transaction that failed after store was called.

width 100% did cause an horizontal scrollbar in firefox and ie. This change breaks the ns4 layout a bit, but I guess we can live with that.

- some related cleanup

- Added the "verbose-security" option in zope.conf.

- Changed the Python security policy implementation to emit verbose 
Unauthorized errors when verbose-security is enabled.

- Also, when verbose-security is enabled, computed roles include the 
name of the permission from which the roles were derived, allowing the 
security policy to reliably discover what permission is missing.

- Fixed tests that didn't pass when verbose security was enabled.

- Moved SimpleItem.__repr__ to a more basic class, where it should have 
been all along.

See also:

http://mail.zope.org/pipermail/zope-dev/2005-June/025019.html