But AFAICT json.py is the only one that supports "canonical json" (and even that support is incomplete - there is no checker / strict decoder). Is there any plan to move this "canonical" stuff into simplejson? I would like to have it available for signature/crypto stuff - unless people think that I should drop all json from signatures, instead using asn.1 and shoehorning our signatures into PKCS7 format (in itself, not a bad fit; but to do the whole job of PKCS7 implies supporting x.509, which is a standard everyone uses but nobody likes).
Jameson On Sat, May 24, 2008 at 1:57 AM, Tomeu Vizoso <[EMAIL PROTECTED]> wrote: > On Sat, May 24, 2008 at 2:56 AM, Martin Langhoff > <[EMAIL PROTECTED]> wrote: > > On Fri, May 23, 2008 at 8:19 PM, Tomeu Vizoso <[EMAIL PROTECTED]> > wrote: > >> Ouch, sorry, I should have been more explicit in that this patch > >> introduces a dependency on cjson. I'm going to send next another patch > >> that falls back to simplejson (slower) if cjson is not available. > > > > Ah, it was pebkac after all. I thought cjson was in the box. > > Simplejson is not though (json.py is). > > simplejson is in joyride (not in u1), json.py is not maintained and > only accepts the basic python types (not dbus.String, for example). > > Regards, > > Tomeu > _______________________________________________ > Devel mailing list > [email protected] > http://lists.laptop.org/listinfo/devel >
_______________________________________________ Devel mailing list [email protected] http://lists.laptop.org/listinfo/devel
