- Collector #928: DateIndex ignored timezones when indexing and
        querying

  - Indexes and Lexicon now much less likely to generate write conflicts.
    Previously *any* concurrent index/unindex operation would conflict

  - Performance and scalability fix for queries

uncreated.

being added to built-in types.

Jamie Heilman discovered it was possible for anonymous users to add
ZClass permission objects.  The newly created permission objects had
no real effect on security, but anonymous users should not be able to
do this anyway, so this patch fixes the bug.

The problem was that PermissionManager never got initiatized.  While I
was here, I took the opportunity to initialize other classes as well,
update the security declaration style, and apply the 'Define
permissions' permission.

Remove signals file, since the only signal you actually need to use is
for log-file rotation.

A few changes to the rST formatting.

  - Exterminate bare excepts
  - Port performance fixes from 2.6 branch
  - Add some comments to questionable areas
  - Simplify where possible
  - Add some spacing for readability (hahahahahah, sorry I crack myself up)
TODO: Fix inefficient __len__ and numObjects implementations

Remove dependancy on PlugInIndexes product by using randint directly to generate rids. randint now works properly with negative number in Python 2.2
Fix bare except. Simplify python implementation of safe_callable

branch *damn CVS*

       with utf-8 encoded strings.

tearDown().  One result is that all tests here except the first died
on Windows with a winlock.error; this is probably unique to lock semantics
on Windows, and doesn't show up at all unless you've installed a modern
Berkeley DB on Windows (unless you do that, these tests don't even try
to run on Windows).

for that the passed-in err[0] may be a string, and when it was died
with an AttributeError in excname().  The verbose_on_error branch does
cater to err[0] being a string, so copied that logic into the showAll
branch.

This prevents problems during test debugging where a logfile isn't
generated and a module might be half-imported.

second of wall-clock time.  That's plenty, except when, e.g., a
burst of network activity takes the CPU away for a second.  Jeremy saw
it fail once yesterday when running Zope-2_6-branch pre-release tests,
and that was unfortunate timing <wink>.  I found that running it in a loop
eventually caused a spurious failure whenever I ran it too.

So, in just this test, boosted the timeout by a factor of 60.  This should
make it astronomically unlikely to fail.  Also sped the test by removing
unneeded .keys() and .sort() calls.  Also switched from using Python's
assert stmt to unittest's assertEqual() facility.

cycle is left behind that includes a SafeMapping, and SafeMappings are not
aware of GC, therefore the cycle can't be collected.  Iterator is also in the
cycle, however, and it does not need a strong reference to the Context object,
since the Context refers to the Iterator.  So Iterators now refer to Context
through a weak reference.

importing AccessControl.User specifically will now function correctly.

reason "import Zope" is often required in unit tests.

from a dict with a float value.

Mapping_update():  This squashed errors raised by PyObject_SetItem(),
changing them to a "not a 2-tuple" TypeError instead.  Unclear why, since
2-tupleness was checked earlier.  Fixed by backporting part of the
ZODB4 BTree construction code, which doesn't have this problem.  Bonus:
it's faster now too.

Make sure test_MultiMapping doesn't rely on the order in which dict
entries are printed.