object or rendering it "with namespace". This also fixes the previously added
test case where importing, instantiating and rendering DateTime would fail.

a method on it. This currently fails, primarily because of a stupidity
in zope.traversing.adapters.traversePathElement and secondarily because
of other funkiness.

by providing PathIterator which (every much like the old PathIterator.Iterator
class) handles its own traversal (only now we use the Zope 3 traversal hooks).

werent' called if they were the result of a path expression, while
all other callables were called. This tests now tests the correct
behaviour (which happens to be already implemented by the Zope 3
TALES engine)

regarding our plans for the other iterator BBB code

a plan how to deal with it.

demonstrates a bug in the very same: The local variable bag was kept
when a new scope was opened, hence it could be polluted by lower scopes.
Zope 3 makes a copy of the local variable bag when it starts a new scope.
This is there Right Thing(tm) to do. This test is now identical to its
Zope 3 equivalent.

the offspring of these insane Zope 2 test fixtures).

thing is unicode now, not string).

XHTML, whitespace fixes, beautifications, etc.)

hook. Stupid, stupid, stupid.

hacks that were in there before.  Tried to reduce the diff to the Zope 2.9 code
a little and moved some content type guessing code to PageTemplateFile where it
really belongs (that also avoids a circular import problem).

macro access happens.

as a base class)

old Zope 2 code.

traversal works.

zope.pagetemplate.pagetemplate.PageTemplate, we need to provide some Zope 2
specifics still.  This isn't a big deal, though, the wrapper code is small.

as an instance by Expressions.py). Minor style cleanup in ZRPythonExpr.py.

Some docstring fixes.

the original thing

aren't evaluated by RestrictedPython. Five needs this.

in Zope 2.10 now, so we could just as well register it here. Gets rid of some
stupid code duplication in Five as well...