<?xml version="1.0" encoding="iso-8859-1"?>
<rdf:RDF xmlns="http://purl.org/rss/1.0/"
         xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" 
         xmlns:dc="http://purl.org/dc/elements/1.1/"
         xmlns:content="http://purl.org/rss/1.0/modules/content/">

<channel rdf:about="http://base-art.net/Articles/27/">
<description>&lt;p&gt;&lt;a class="reference" href="http://www.reportlab.org/pyrxp.html"&gt;PyRXP&lt;/a&gt; claims to be the fastest Python XML parser around... but this has a price. Once XML is parsed, you get a tree structured as tuples, lists and dictionnaries. While this is very Pythonic, it's not so trivial to write/read code handling such a tree.&lt;/p&gt;
&lt;p&gt;People at Reportlab argue about that for speed. Dealing with classes in Python is mem hungry, so they use only basic data structures (tuples,list,...). I can understand that but i believe it's an &lt;cite&gt;extremist&lt;/cite&gt; point. Finding a balance between the DOM API (which is &lt;cite&gt;extremist&lt;/cite&gt; too :) and such structures could turn to be more popular, maybe a Python &lt;cite&gt;xml_node&lt;/cite&gt; builtin type ...&lt;/p&gt;
</description>
<link>http://base-art.net/Articles/27/</link>
<title>Comments on article "About PyRXP"</title>



<items>
<rdf:seq>

<rdf:li rdf:resource="http://base-art.net/Comments/196/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/77/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/73/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/72/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/71/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/70/"/>

<rdf:li rdf:resource="http://base-art.net/Comments/69/"/>

</rdf:seq>
</items>


</channel>


<item rdf:about="http://base-art.net/Comments/196/">
<dc:date>2006-03-12T20:56:07.000006+01:00</dc:date>
<title>Dj Mixer on About PyRXP</title>
<link>http://base-art.net/Comments/196/</link>
<author>Dj Mixer</author>
<description>
&lt;p&gt;ReportLab are proud to present pyRXP version 0.9, the fastest validating XML parser available for Python, and quite possibly anywhere :-).&lt;/p&gt;
&lt;p&gt;This is not a full DOM implementation, but we think it will do what 90% of the people want, in 10% of the time. And with validation. Enjoy!&lt;/p&gt;
&lt;p&gt;&lt;a class="reference" href="http://www.reportlab.co.uk/svn/public/reportlab/trunk/rl_addons/pyRXP/"&gt;http://www.reportlab.co.uk/svn/public/reportlab/trunk/rl_addons/pyRXP/&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;&lt;a class="reference" href="http://mp3djay.com"&gt;http://mp3djay.com&lt;/a&gt;&lt;/p&gt;

</description>
</item>

<item rdf:about="http://base-art.net/Comments/77/">
<dc:date>2004-12-26T10:31:40.000006+01:00</dc:date>
<title>Fredrik on About PyRXP</title>
<link>http://base-art.net/Comments/77/</link>
<author>Fredrik</author>
<description>
&lt;p&gt;According to my large-file benchmarks (large files, mostly ASCII, lot of elements, few attributes), Gnosis is nearly &lt;em&gt;10 times slower&lt;/em&gt; than RXPU, and uses twice as much memory.&lt;/p&gt;
&lt;p&gt;ElementTree 1.2.1 (and later) under Python 2.3 (or later) is as close as you can get with a pure-Python solution, and that's still over 4 times slower and needs 25% more memory.  The standard minidom is a little slower than that (but still faster than gnosis), but is extremely memory-hungry.&lt;/p&gt;
&lt;p&gt;So don't trust the pundits: RXPU is &lt;em&gt;extremely&lt;/em&gt; fast, and very memory-efficient (and RXP is even faster, but more limited).&lt;/p&gt;

</description>
</item>

<item rdf:about="http://base-art.net/Comments/73/">
<dc:date>2004-12-23T11:42:23.000003+01:00</dc:date>
<title>phil on About PyRXP</title>
<link>http://base-art.net/Comments/73/</link>
<author>phil</author>
<description>
&lt;p&gt;Ian,&lt;/p&gt;
&lt;p&gt;Yes the tuple-list-dictionnary representation is fine, i'm ok with that. But then, you have to mix lamba forms, map() calls to extract usefull informations from the tree. I don't use such coding tricks very often (maybe should i ?), so it's not easy.&lt;/p&gt;

</description>
</item>

<item rdf:about="http://base-art.net/Comments/72/">
<dc:date>2004-12-23T09:23:54.000003+01:00</dc:date>
<title>Ian Bicking on About PyRXP</title>
<link>http://base-art.net/Comments/72/</link>
<author>Ian Bicking</author>
<description>
I can't speak to the Unicode issues (assuming that's the flaw people are talking about with PyRXP).  But I used RXP a while ago, and it seemed fine to me.  Honestly, I don't find the tuple-and-list representation to be a problem at all.  Certainly a representation using an efficient type would be preferable, but as long as you aren't actually exposing the tuples outside of your domain library, they seem like a reasonable compromise.  Maybe with __slots__ (which postdate PyRXP?) the memory efficiency isn't as much of an issue -- though object construction time would still be a concern (assuming that tuples and lists are very fast to create).
</description>
</item>

<item rdf:about="http://base-art.net/Comments/71/">
<dc:date>2004-12-21T19:35:43.000001+01:00</dc:date>
<title>phil on About PyRXP</title>
<link>http://base-art.net/Comments/71/</link>
<author>phil</author>
<description>
Ok, so i forget PyRXP forever ... i'm impatient to see PyRXPU compared to others (real?) parsers. The PyRXP's homepage is wrong so ...
</description>
</item>

<item rdf:about="http://base-art.net/Comments/70/">
<dc:date>2004-12-20T18:33:35+01:00</dc:date>
<title>verbat on About PyRXP</title>
<link>http://base-art.net/Comments/70/</link>
<author>verbat</author>
<description>
stop using PyRXP now. It's not an xml parser, and it should eb replaced by PyRXPU ASAP. Then, it would be slow, obviously.
</description>
</item>

<item rdf:about="http://base-art.net/Comments/69/">
<dc:date>2004-12-19T19:01:43.000006+01:00</dc:date>
<title>anon on About PyRXP</title>
<link>http://base-art.net/Comments/69/</link>
<author>anon</author>
<description>
&lt;p&gt;&lt;a class="reference" href="http://www-106.ibm.com/developerworks/library/x-matters39.html"&gt;http://www-106.ibm.com/developerworks/library/x-matters39.html&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;I'm pretty sure gnosis.xml.objectify is quite close in speed to pyRXP--especially if you compare to the Unicode-enabled pyRXPU that actually parses XML (rather than some XML-like non-standard language: see Uche Ogbuji's comments on this).&lt;/p&gt;
&lt;p&gt;At the same time: gnosis.xml.objectify nodes are as Pythonic as you can possibly get.  Even more so, IMO, than those in ElementTree, for example.&lt;/p&gt;

</description>
</item>


</rdf:RDF>
