<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: simple_json 1.0</title>
	<atom:link href="http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/feed/" rel="self" type="application/rss+xml" />
	<link>http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/</link>
	<description>Bob's Rants</description>
	<pubDate>Fri, 05 Sep 2008 21:40:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Koen</title>
		<link>http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/#comment-2749</link>
		<dc:creator>Koen</dc:creator>
		<pubDate>Tue, 03 Jan 2006 15:32:21 +0000</pubDate>
		<guid isPermaLink="false">http://bob.pythonmac.org/?p=189#comment-2749</guid>
		<description>Okay, I have just checked my JSONReader against SimpleJSON on a 6MB and a 4.5MB file.
On a Athlon XP 2000+ I get the following times:
6 MB file: 1.2s for JSONReader, 31.5s for SimpleJSON.
4.5 MB file: 1.1s for JSONReader, 24.1s for SimpleJSON.

I have to make some notes:
- JSONReader uses the standard C API to open a file through a filename. If I read the file into memory completely in Python and then use JSONReader's from-string reading API (e.g. not using the standard C file API), then times are 1.3s, 1.1s respectively. Supporting a StringIO API is non-trivial because of the lex/yacc basis, I haven't looked at this yet. Perhaps it is possible to make it use a .read() interface, but I think it will be hard.
- Only works on ASCII strings. Characters 128-255 are kept as normal characters and not interpreted at all. So they should come out the way they come in (I do not rely on this behavior, I only use \uXXXX).</description>
		<content:encoded><![CDATA[<p>Okay, I have just checked my JSONReader against SimpleJSON on a 6MB and a 4.5MB file.<br />
On a Athlon XP 2000+ I get the following times:<br />
6 MB file: 1.2s for JSONReader, 31.5s for SimpleJSON.<br />
4.5 MB file: 1.1s for JSONReader, 24.1s for SimpleJSON.</p>
<p>I have to make some notes:<br />
- JSONReader uses the standard C API to open a file through a filename. If I read the file into memory completely in Python and then use JSONReader&#8217;s from-string reading API (e.g. not using the standard C file API), then times are 1.3s, 1.1s respectively. Supporting a StringIO API is non-trivial because of the lex/yacc basis, I haven&#8217;t looked at this yet. Perhaps it is possible to make it use a .read() interface, but I think it will be hard.<br />
- Only works on ASCII strings. Characters 128-255 are kept as normal characters and not interpreted at all. So they should come out the way they come in (I do not rely on this behavior, I only use \uXXXX).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nick</title>
		<link>http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/#comment-2747</link>
		<dc:creator>nick</dc:creator>
		<pubDate>Thu, 29 Dec 2005 17:19:23 +0000</pubDate>
		<guid isPermaLink="false">http://bob.pythonmac.org/?p=189#comment-2747</guid>
		<description>This is a much better implementation, good job.  But to be fair, json-py is a straight Python implementation of the Javascript reference implementation.</description>
		<content:encoded><![CDATA[<p>This is a much better implementation, good job.  But to be fair, json-py is a straight Python implementation of the Javascript reference implementation.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bob</title>
		<link>http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/#comment-2740</link>
		<dc:creator>bob</dc:creator>
		<pubDate>Tue, 27 Dec 2005 02:14:04 +0000</pubDate>
		<guid isPermaLink="false">http://bob.pythonmac.org/?p=189#comment-2740</guid>
		<description>It would be nice to have as an optional extension, like elementree vs cElementTree.  Do you have benchmarks?</description>
		<content:encoded><![CDATA[<p>It would be nice to have as an optional extension, like elementree vs cElementTree.  Do you have benchmarks?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Koen</title>
		<link>http://bob.pythonmac.org/archives/2005/12/26/simple_json-10/#comment-2733</link>
		<dc:creator>Koen</dc:creator>
		<pubDate>Mon, 26 Dec 2005 20:53:11 +0000</pubDate>
		<guid isPermaLink="false">http://bob.pythonmac.org/?p=189#comment-2733</guid>
		<description>Hmm, interesting. This summer I wrote a JSONReader C module (basically it will parse into native Python structures through a Python extension) with very high efficiency. I offered it to be included into json-py, and the author said yes, but I haven't heard from him since.
The module is still unreleased because of this, so maybe it can find it's way into Simple-JSON? It's only a decoder, not an encoder. Mail me if you're interested (I'll be on vacation the coming week though).</description>
		<content:encoded><![CDATA[<p>Hmm, interesting. This summer I wrote a JSONReader C module (basically it will parse into native Python structures through a Python extension) with very high efficiency. I offered it to be included into json-py, and the author said yes, but I haven&#8217;t heard from him since.<br />
The module is still unreleased because of this, so maybe it can find it&#8217;s way into Simple-JSON? It&#8217;s only a decoder, not an encoder. Mail me if you&#8217;re interested (I&#8217;ll be on vacation the coming week though).</p>
]]></content:encoded>
	</item>
</channel>
</rss>
