From 2915dd7103730580a63760a8b4166d2137666920 Mon Sep 17 00:00:00 2001 From: Eli Bendersky Date: Thu, 31 Oct 2013 05:53:39 -0700 Subject: [PATCH] Issue #19452: Clarify the documentation of iterparse w.r.t. events argument. In 3.3 iterparse accepts a tuple in events (the C accelerator enforces this). This limitation was lifted in Python 3.4 --- Doc/library/xml.etree.elementtree.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Doc/library/xml.etree.elementtree.rst b/Doc/library/xml.etree.elementtree.rst index 86739615ebd..cf652199e36 100644 --- a/Doc/library/xml.etree.elementtree.rst +++ b/Doc/library/xml.etree.elementtree.rst @@ -379,7 +379,7 @@ Functions Parses an XML section into an element tree incrementally, and reports what's going on to the user. *source* is a filename or :term:`file object` - containing XML data. *events* is a list of events to report back. The + containing XML data. *events* is a tuple of events to report back. The supported events are the strings ``"start"``, ``"end"``, ``"start-ns"`` and ``"end-ns"`` (the "ns" events are used to get detailed namespace information). If *events* is omitted, only ``"end"`` events are reported.