[Lxml-checkins] r55084 - in lxml/trunk: . src/lxml

scoder at codespeak.net scoder at codespeak.net
Wed May 21 21:45:29 CEST 2008


Author: scoder
Date: Wed May 21 21:45:28 2008
New Revision: 55084

Modified:
   lxml/trunk/   (props changed)
   lxml/trunk/CHANGES.txt
   lxml/trunk/src/lxml/iterparse.pxi
Log:
 r4249 at delle:  sbehnel | 2008-05-20 21:50:20 +0200
 work around stupid MSVC string size limit


Modified: lxml/trunk/CHANGES.txt
==============================================================================
--- lxml/trunk/CHANGES.txt	(original)
+++ lxml/trunk/CHANGES.txt	Wed May 21 21:45:28 2008
@@ -25,6 +25,8 @@
 Bugs fixed
 ----------
 
+* Windows build was broken.
+
 * Rare crash when serialising to a file object with certain encodings.
 
 Other changes

Modified: lxml/trunk/src/lxml/iterparse.pxi
==============================================================================
--- lxml/trunk/src/lxml/iterparse.pxi	(original)
+++ lxml/trunk/src/lxml/iterparse.pxi	Wed May 21 21:45:28 2008
@@ -307,46 +307,47 @@
 
 cdef class iterparse(_BaseParser):
     u"""iterparse(self, source, events=("end",), tag=None, attribute_defaults=False, dtd_validation=False, load_dtd=False, no_network=True, remove_blank_text=False, remove_comments=False, remove_pis=False, encoding=None, html=False, schema=None)
-    Incremental parser.
 
-    Parses XML into a tree and generates tuples (event, element) in a
-    SAX-like fashion. ``event`` is any of 'start', 'end', 'start-ns',
-    'end-ns'.
-
-    For 'start' and 'end', ``element`` is the Element that the parser just
-    found opening or closing.  For 'start-ns', it is a tuple (prefix, URI) of
-    a new namespace declaration.  For 'end-ns', it is simply None.  Note that
-    all start and end events are guaranteed to be properly nested.
-
-    The keyword argument ``events`` specifies a sequence of event type names
-    that should be generated.  By default, only 'end' events will be
-    generated.
-
-    The additional ``tag`` argument restricts the 'start' and 'end' events to
-    those elements that match the given tag.  By default, events are generated
-    for all elements.  Note that the 'start-ns' and 'end-ns' events are not
-    impacted by this restriction.
-
-    The other keyword arguments in the constructor are mainly based on the
-    libxml2 parser configuration.  A DTD will also be loaded if validation or
-    attribute default values are requested.
-
-    Available boolean keyword arguments:
-      - attribute_defaults - read default attributes from DTD
-      - dtd_validation     - validate (if DTD is available)
-      - load_dtd           - use DTD for parsing
-      - no_network         - prevent network access for related files
-      - remove_blank_text  - discard blank text nodes
-      - remove_comments    - discard comments
-      - remove_pis         - discard processing instructions
-      - strip_cdata        - replace CDATA sections by normal text content (default: True)
-      - compact            - safe memory for short text content (default: True)
-      - resolve_entities   - replace entities by their text value (default: True)
-
-    Other keyword arguments:
-      - encoding           - override the document encoding
-      - schema             - an XMLSchema to validate against
-    """
+Incremental parser.
+
+Parses XML into a tree and generates tuples (event, element) in a
+SAX-like fashion. ``event`` is any of 'start', 'end', 'start-ns',
+'end-ns'.
+
+For 'start' and 'end', ``element`` is the Element that the parser just
+found opening or closing.  For 'start-ns', it is a tuple (prefix, URI) of
+a new namespace declaration.  For 'end-ns', it is simply None.  Note that
+all start and end events are guaranteed to be properly nested.
+
+The keyword argument ``events`` specifies a sequence of event type names
+that should be generated.  By default, only 'end' events will be
+generated.
+
+The additional ``tag`` argument restricts the 'start' and 'end' events to
+those elements that match the given tag.  By default, events are generated
+for all elements.  Note that the 'start-ns' and 'end-ns' events are not
+impacted by this restriction.
+
+The other keyword arguments in the constructor are mainly based on the
+libxml2 parser configuration.  A DTD will also be loaded if validation or
+attribute default values are requested.
+
+Available boolean keyword arguments:
+ - attribute_defaults: read default attributes from DTD
+ - dtd_validation: validate (if DTD is available)
+ - load_dtd: use DTD for parsing
+ - no_network: prevent network access for related files
+ - remove_blank_text: discard blank text nodes
+ - remove_comments: discard comments
+ - remove_pis: discard processing instructions
+ - strip_cdata: replace CDATA sections by normal text content (default: True)
+ - compact: safe memory for short text content (default: True)
+ - resolve_entities: replace entities by their text value (default: True)
+
+Other keyword arguments:
+ - encoding: override the document encoding
+ - schema: an XMLSchema to validate against
+""" # stupid, stupid MSVC has a 2048 bytes limit for strings!!!
     cdef object _tag
     cdef object _events
     cdef readonly object root


More information about the lxml-checkins mailing list