http://bugs.python.org/issue2746 (existing issue (processing
instruction) - patch & test case added)
http://bugs.python.org/issue6230 (repr bug)
http://bugs.python.org/issue6231 (ElementInclude bug)
http://bugs.python.org/issue6232 (suggested improvements to
test_xml_etree.py and test_xml_etree_c.py
--
Neil Muller
drnlm...@gmail.com
I've got a gmail account. Why haven't I become cool?
http://bugs.python.org/issue2746 (existing issue (processing
instruction) - patch& test case added)
http://bugs.python.org/issue6230 (repr bug)
http://bugs.python.org/issue6231 (ElementInclude bug)
http://bugs.python.org/issue6232 (suggested improvements to
test_xml_etree.py and test_xml_etree_c.py
</pre></blockquote><pre wrap><!---->
I didn't see any comments about the cElementTree {Expat,Syntax}Error and
bug_xmltoolkit55 issues. Should those be separate bugs or comments on
issue6232?
--J
<div class="moz-txt-sig">--
</div></pre></div>
Eep! My mail client broke something. Trying again with a real text version:
Neil Muller wrote:
> The focus
> on the test wirting day was on ElementTree - we uncovered a
> few bugs in the process, so the following issues were filed/ touched:
>
> http://bugs.python.org/issue2746 (existing issue (processing
> instruction) - patch& test case added)
> http://bugs.python.org/issue6230 (repr bug)
> http://bugs.python.org/issue6231 (ElementInclude bug)
> http://bugs.python.org/issue6232 (suggested improvements to
> test_xml_etree.py and test_xml_etree_c.py
I didn't see any comments about the cElementTree {Expat,Syntax}Error and
bug_xmltoolkit55 issues. Should those be separate bugs or comments on
issue6232?
--J
--
I'm inclined to say they should be filed as separate issues, and the
new issues should be mentioned in issue6232.
We should also extend the tests to cover
http://bugs.python.org/issue3409 & http://bugs.python.org/issue1777