[issue9257] cElementTree iterparse requires events as bytes; ElementTree uses strings

2012-02-10 Thread Eric Talevich
Eric Talevich added the comment: Well, this is not the best month for me to try digging into a new codebase... I would not mind if someone else did the patch for this. -- ___ Python tracker <http://bugs.python.org/issue9

[issue9257] cElementTree iterparse requires events as bytes; ElementTree uses strings

2012-02-08 Thread Eric Talevich
Eric Talevich added the comment: It's more-or-less fixed in Python 3.2: - With cElementTree, both bytes and strings are accepted for events; - With ElementTree, only strings are accepted, and bytes raise a ValueError (unknown event). A small inconsistency remains, but it's fine t

[issue9257] cElementTree iterparse requires events as bytes; ElementTree uses strings

2010-08-12 Thread Eric Talevich
Eric Talevich added the comment: This bug seems to be still present in Python 3.1.2. (Unless I'm doing something wrong.) Was r78942 included in the 3.1.2 release? -- ___ Python tracker <http://bugs.python.org/i

[issue2734] 2to3 converts long(itude) argument to int

2010-07-22 Thread Eric Talevich
Eric Talevich added the comment: This issue still occurs when the name "long" is a function argument: def double(long): return long * 2 2to3 converts it to: def double(long): return int * 2 Should I file a new bug, or can someone reopen this? -- nosy: +eri

[issue9257] cElementTree iterparse requires events as bytes; ElementTree uses strings

2010-07-13 Thread Eric Talevich
New submission from Eric Talevich : In xml.etree, ElementTree and cElementTree implement different interfaces for the iterparse function/class. In ElementTree, the argument "events" must be a tuple of strings: from xml.etree import ElementTree as ET for result in ET.iterparse(&#