be taken care of by the DefaultHandler that I'm adding to TALParser.

the generated XML for repeated elements.  This also required slightly
refactoring the way beginScope/endScope are emitted for repeated
element: now we open and close two scopes if an element has both a
tal:define and a tal:repeat attribute -- just like TALParser does.

preceding whitespace into the repeated stuff for a loop: if a repeated
element is preceded by a newline possibly followed by whitespace,
repeat that newline and whitespace for each loop iteration.  This
makes the generated XML look better.

following whitespace back out of the instruction stream.  This can be
used to make the output for loops look nicer.

redundant namespace declaration for the xml prefix when we see <elem
xml:attr="">.

xml:attr=""> without an xmlns declaration.

TALCompiler, and caused a subtle problem when integrating into
PresentationTemplates.

to try to handle extreme cases where the _dav_writelocks object is
completely hosed.

  messages.

  messages.

- Now that splitParts() is fixed to lose the last part if it's empty,
  don't break on empty parts.

  messages.

- Fix splitParts() to lose the last part if it's empty.

overhead in ZEO situations and is more expensive than its worth.

object itself.

* Add unit test to exercise Collector #1959, "FieldIndexes won't store
  Zero's" (but I can't verify the hypothesis, dammit!)

Changed getobject logic to log on failure and raise a meaningful exception instead of raising unauthorized and causing a browser auth box to pop up.

extra semicolons at end, like Python allows extra commas.

compiling directly from DOM!