Eli Bendersky added the comment:
Thanks for the report, Peter. This is indeed a documentation fix for Python
3.3; note that in 3.4 (default branch), the restriction was lifted and
iterparse now accepts any iterable sequence. The documentation also reflects
that (saying that 'events' is a
Changes by Eli Bendersky eli...@gmail.com:
--
stage: - needs patch
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19452
___
___
Python-bugs-list
Roundup Robot added the comment:
New changeset e6941225e014 by Eli Bendersky in branch '3.3':
Issue #19452: Clarify the documentation of iterparse w.r.t. events argument.
http://hg.python.org/cpython/rev/e6941225e014
New changeset 2a996cecf762 by Eli Bendersky in branch 'default':
Null merge
Changes by Eli Bendersky eli...@gmail.com:
--
resolution: - fixed
stage: needs patch - committed/rejected
status: open - closed
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19452
___
New submission from Peter Harris:
Documentation on python website says:
xml.etree.ElementTree.iterparse(source, events=None, parser=None)
Parses an XML section into an element tree incrementally, and reports what’s
going on to the user. source is a filename or file object containing XML
Stefan Behnel added the comment:
How about actually allowing a list in addition to a tuple? And, in fact, any
sequence? I can't see a reason not to.
For reference, lxml only expects it to be either None or an iterable.
Essentially, I consider it more of a set-like filter, since the linear
Peter Harris added the comment:
Yeah it would make sense to accept any iterable, but I'm only proposing a
documentation fix not a feature enhancement.
--
___
Python tracker rep...@bugs.python.org
http://bugs.python.org/issue19452
