Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
ab2a76c8
Commit
ab2a76c8
authored
Apr 20, 2013
by
Eli Bendersky
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update ET documentation reprhasing the mention of the new IncrementalParser in
the doc for iterparse.
parent
bf05df23
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
5 additions
and
4 deletions
+5
-4
Doc/library/xml.etree.elementtree.rst
Doc/library/xml.etree.elementtree.rst
+5
-4
No files found.
Doc/library/xml.etree.elementtree.rst
View file @
ab2a76c8
...
...
@@ -387,6 +387,11 @@ Functions
:class:`XMLParser` parser is used. Returns an :term:`iterator` providing
``(event, elem)`` pairs.
Note that while :func:`iterparse` builds the tree incrementally, it issues
blocking reads on *source* (or the file it names). As such, it's unsuitable
for asynchronous applications where blocking reads can't be made. For fully
asynchronous parsing, see :class:`IncrementalParser`.
.. note::
:func:`iterparse` only guarantees that it has seen the ">"
...
...
@@ -397,10 +402,6 @@ Functions
If you need a fully populated element, look for "end" events instead.
.. note::
For real event-driven parsing, see :class:`IncrementalParser`.
.. function:: parse(source, parser=None)
Parses an XML section into an element tree. *source* is a filename or file
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment