this fixes the Windows crashes?

checkSimpleTransactionalUndo(): Modify tests to check zombification
and subsequent re-birth of objects via transactionalUndo().

works by writing a metadata record which contains a special lrevid
(pickle pointer).  Upon loading a zombified object, naive applications
will get a KeyError as would be expected for loading a non-existant
object.

The actual exception though is ObjectDoesNotExist -- derived from
KeyError -- which contains a `revid' attribute pointing to the
revision of the object which zombified it.  Thus, by undoing this
revid, the object can be reborn to its initial state.

Specifically,

ObjectDoesNotExist: New exception, derived from KeyError.

load(): If an object's metadata has an lrevid with the special `dne'
value (64-bits full of 1's), the object is a zombie and
ObjectDoesNotExist is raised.

transactionalUndo(): If prevrevid for the revision we're undoing is
zero, it means that we're undoing the object's creation.  Instead of
raising an UndoError, write a new metadata record containing the
original record, but with lrevid == dne, and prevrevid == tid.

This change also contains initial (untested) support for pack(),
specifically,

_zaprevision(): pack doesn't happen in a transaction, so remove the
txn argument.  Add the referencesf argument, passed from the pack()
call.

pack(): Initial implementation.  Seems fairly simple really (too
simple? ;)

XMLParserTestCase.check_bad_nesting():
    Use self.fail() instead of naming AssertionError directly; how PyUnit
    deals with the error is it's problem, not ours.  ;-)

Fix two buffer boundary issues; this restores this to passing the test
suite without any large restructuring.

Guido & I will be looking at how this is structured later; buffer
boundary checks will make this nearly unmaintainable if we can't
bring about a better structure to the code.  (Better tests would also
be nice!)

character at a time.  This uncovers two new bugs in HTMLParser that
I'm going to attack next.

default true.  When this is false, structure insertion without
attribute replacement does not parse the inserted text.  This is
(expected to be) much faster, but allows invalid HTML/XML to be
inserted, so it is off by default.

Evan can choose to turn this on in ZPT if he's more concerned about
efficiency than about correctness. :-)

<script> and <style> elements aren't mangled.

By nature of the parser, bare < and & cannot occur in the input data
(the parser raises an exception when it encounters these); bare > is
harmless.

buffer boundaries in the middle of the cdata stretch.

Fixed this, and added a clear_cdata_mode() callback after a successful
</endtag>.  (I hope this doesn't break other things.  This parser is
getting horribly ad-hoc. :-( )

code.

All test should succeed now (both TAL/test/run.py and TAL/runtest.py).

longer generated.

Also fix the test for <img src tal:attributes="src nothing">.

XMLNS attributes) in rendered output, with an option to keep the old
behavior.

HTMLTALParser.py, TALParser.py:
    Mark TAL, METAL and TAL/METAL-related XMLNS attributes in the
    attribute list; the old macroHack marking is subsumed in this.
    The marking is a third value in the list item describing the
    attribute, saying "tal", "metal" or "xmlns".  All TAL and METAL
    attributes are marked; only XMLNS attributes whose namespace URI
    value is the special marker for TAL or METAL are marked.

TALInterpreter.py:
    - Get rid of the non-functional 'html' keyword argument.
    - Add new 'showtal' keyword argument to constructor; this defaults
      to -1, which means that the value should default to 0 if TAL
      expansion is requested (through the 'tal' keyword argument) and
      1 if TAL expansion is not requested.
    - In do_startEndTag(), don't special-case empty HTML tags; this is
      already taken care of by TALGenerator.
    - Implement the showtal behavior: when this flag is false, don't
      output TAL, METAL and XMLNS attributes (that are marked as such
      by the parser).
    - Fix a bug: <img src="foo" tal:attributes="src nothing"> should
      render as <img>, not as <img src>.

TALDefs.py:
    Bumped TAL_VERSION to "1.0.1"

driver.py:
    New command line option -t to show tal in output

README.txt:
    Update TO DO list.

At: http://classic.zope.org:8080/Collector/Collector/2141/sview

Submitter:  John Eikenberry

Email:  jae@kavi.com

Description: We have a large query implemented via a SQL Method. We've
been messing with it to get the most speed out of it, and noticed a
large hit in the __init__() method on the Results class. We found that
with this simple tweak (see included patch) we got around a 180% speed
up. Not a ton, but pretty good for changing 3 lines of code.

(There's really not a good reason for asynchat to be in
Python's standard lib.)

CVS (1.9).

as I hate line-continuation characters.

Remove done item from TO DO list (CDATA content support).

to a directory other than the ZEO package directory.

Add general support for CDATA element content, enabled by default for
<script> and <style> elements since those are the ones I found in HTML 4.01.

Added a test case to make sure <script> and <style> elements are handled
correctly.

set or cleared by specifying any true or false value.

(XXX I wonder if this should be recognized at compile time rather than
at interpretation time; oh well, this works.)

    more strict about matchnig only what's legal.  The expression ends
    up being a bit more complex, and needs additional checks to be
    done on what follows.

HTMLParser.check_for_whole_start_tag():  Helper method that uses
    locatestarttagend, performs the required additional checks, and
    determines whether we've actually found the end of the start tag,
    are at a buffer boundary, or have encountered an syntactical
    error.


HTMLParser.parse_starttag():  Use check_for_whole_start_tag() to see
    if we really have the start tag.

HTMLParseError.__init__():  Simplify assertion.


This should close ZPT(18).

Revise a test that requires "<tag attr=>" to be accepted -- it is not!

Add a check to ensure it raises an HTMLParseError.

Revise a test that requires "<tag attr=>" to be accepted -- it is not!