[Sugar-devel] Rationale behind the JSON -> CJSON switch in Sugar codebase?

Tomeu Vizoso tomeu at sugarlabs.org
Thu Nov 12 10:40:31 EST 2009

On Thu, Nov 12, 2009 at 15:59, Martin Langhoff
<martin.langhoff at gmail.com> wrote:
> This commit http://git.sugarlabs.org/projects/sugar/repos/mainline/commits/ee4535c98ae74347e7072909d49dcf8a5e16ca7b
> breaks importing Journal Entry Bundles, and I think it's just the tip
> of the iceberg.
> The commit msg is pretty factual but doesn't add much to what the diff
> says. There must have been a reason to do it.
> Relevant trac tickets:
>  - http://dev.sugarlabs.org/ticket/1553
>  - http://dev.laptop.org/ticket/9651

If I read correctly, you are implying that the cjson module reads
canonical json, when it's just an alternative implementation of plain
json for python that used to be the fastest available in the time.
Right now just using the json module in python 2.6 may be best as the
parser is a C module (AFAIR).

Is because of a bug in cjson why those files aren't being parsed?



> cheers,
> m
> --
>  martin.langhoff at gmail.com
>  martin at laptop.org -- School Server Architect
>  - ask interesting questions
>  - don't get distracted with shiny stuff  - working code first
>  - http://wiki.laptop.org/go/User:Martinlanghoff

«Sugar Labs is anyone who participates in improving and using Sugar.
What Sugar Labs does is determined by the participants.» - David

More information about the Sugar-devel mailing list