in ZServer/HTTPServer

      - Collector #2116: sequence.sort() did not work properly
        locale related comparison methods

http://www.zope.org/Collectors/Zope/2118

 Log message for revision 68451:
  Allow access to ZopeIterator/PathIterator API from restricted Python
  (e.g. python expressions)

adapter to be present even when traversing just dicts. No problem, we can
set it up quite easily.

This basically finishes this branch. All tests pass, some 3rd party apps
have been tested with it. There are a few test failures in the CMF and
others (e.g. Plone), but that's mostly "their fault" (incorrect or
unexpected usage of certain things).

- Apply usual tal:omit-tag fix to make the element carrying i18n:name go away
- Disable a test that was testing madness (mixing unicode and encoded strings)

* tal:replace now emits something different (optTag)
* constructs with i18n:name emits more complicated bytecode (i18nVariable, etc.)
  to cope with behavioural changes (see http://zope.org/Collectors/Zope3-dev/301)
* probably some more that aren't very interesting (if these any of this is
  interesting at all)

i18n:name and i18n:translate on the same element is now supported. Moreover,
i18n:translate isn't automatically assumed for those elements with i18n:name.
Also, the element that i18n:name is on isn't automatically removed anymore.
You'll have to use tal:omit-tag to explicitly make it go away.

For more info, see http://zope.org/Collectors/Zope3-dev/301.

into something general, make PathExpr deal with Zope 2 exceptions.

is fixed. Because then we need to have an ITraversable registered evne when
traversing dicts. For now this doesn't do harm.

(boboTraverseAwareSimpleTraverse) with a request. Since zope.app has
already solved this problem (and I copied zope.app's approach in the
traverser), we can just simply reuse zope.app's code here. Yes, it
adds another dependency on zope.app, but at least we're not duplicating
code.

All Zope 2 tests should be passing now...