proeprties properly (in fact they were unhandled)

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.

Port from 2.7 branch.

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.

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

This was also done on Zope-2_8-branch.

- 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

Clarify, correct, expand.

      - Collector #1808: manage_convertIndexes no longer tries to change the
        index types causing some trouble with CMF.

install products that were installed by Zope during startup.

Import pywintypes first.

Mark Hammond's checkin comment for Zope 2.7's WinSignalHandler.py,
rev 1.1.2.2:

"""
As at pywin32-204, we must ensure pywintypes is the first win32 module
imported in our process, otherwise we can end up with 2 pywintypesxx.dll
instances in our process resulting in:
TypeError: The object is not a PySECURITY_ATTRIBUTES object
"""

Mysterious error popup boxes have also been seen, on boxes with a
pre-pywin32-204 installation leaving pywin32 DLLs in the system32
directory.

Collector #1803: Fixed InitializeClass for some corner case.

Mark Hammond's original checkin comment:

As at pywin32-204, we must ensure pywintypes is the first win32 module
imported in our process, otherwise we can end up with 2 pywintypesxx.dll
instances in our process resulting in:
TypeError: The object is not a PySECURITY_ATTRIBUTES object

Mark Hammond's original checkin comment:

As at pywin32-204, we must ensure pywintypes is the first win32 module
imported in our process, otherwise we can end up with 2 pywintypesxx.dll
instances in our process resulting in:
TypeError: The object is not a PySECURITY_ATTRIBUTES object

than GET or HEAD while omitting the stdin argument.

than GET or HEAD while omitting the stdin argument.

Collector http://www.zope.org/Collectors/Zope/1797 : 304 responses require collaboration from http accelerated cache manager.  (see also http://www.zope.org/Collectors/Zope/683).

Collector http://www.zope.org/Collectors/Zope/1797 : 304 responses require collaboration from http accelerated cache manager.  (see also http://www.zope.org/Collectors/Zope/683).

Merge from product_installation_tracking branch. The product install now keeps a dict of installed products, and ZopeTestCase checks it, so not to install products twice.

Merge from product_installation_tracking branch. The product install now keeps a dict of installed products, and ZopeTestCase checks it, so not to install products twice.

- added some basic conformance tests

Note that this is just a first step:
- there are still some z2 interfaces that are not bridged to z3 interfaces
- the bridging introduces a dependency on Five, non-dynamic z3 interfaces might be more suitable (but add redundant code)
- 'implements' declarations are not complete
- many interfaces have unresolved XXX coments

  Update Five to release 1.0.1.