On Sat, Sep 27, 2008 at 23:24, Bob Ippolito <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 27, 2008 at 2:10 PM, Arnar Birgisson <[EMAIL PROTECTED]> wrote:
>> On Sat, Sep 27, 2008 at 22:13, Bob Ippolito <[EMAIL PROTECTED]> wrote:
>>> If you give it unicode input, it will decode to unicode. Basically it
>>
On Sat, Sep 27, 2008 at 2:10 PM, Arnar Birgisson <[EMAIL PROTECTED]> wrote:
> On Sat, Sep 27, 2008 at 22:13, Bob Ippolito <[EMAIL PROTECTED]> wrote:
>> If you give it unicode input, it will decode to unicode. Basically it
>> scans through the str until it finds non-ASCII, escape, or end quote.
>> I
On Sat, Sep 27, 2008 at 22:13, Bob Ippolito <[EMAIL PROTECTED]> wrote:
> If you give it unicode input, it will decode to unicode. Basically it
> scans through the str until it finds non-ASCII, escape, or end quote.
> If it finds the end quote first it will just allocate a new string
> with exactly
On Sat, Sep 27, 2008 at 11:35 AM, Arnar Birgisson <[EMAIL PROTECTED]> wrote:
> Hi Bob,
>
> On Sat, Sep 27, 2008 at 20:16, Bob Ippolito <[EMAIL PROTECTED]> wrote:
>> Even without the C speedups, it's several times faster. With the C
>> speedups, it's WAY faster. I highly recommend that everyone upda
Hi Bob,
On Sat, Sep 27, 2008 at 20:16, Bob Ippolito <[EMAIL PROTECTED]> wrote:
> Even without the C speedups, it's several times faster. With the C
> speedups, it's WAY faster. I highly recommend that everyone update
> their frameworks to use the latest code.
Excellent stuff!
> There aren't real
I spent a fair amount of time this week profiling, benchmarking, and
optimizing simplejson. simplejson 2.0.0 includes the following
enhancements:
http://pypi.python.org/pypi/simplejson
* optimized Python encoding path
* optimized Python decoding path
* optimized C encoding path
* optimized C deco
