> * Do we want to make TurboJson configurable in TG 1.0 as well? I don't mind, but Florent is the one to decide if feature creep is in order.
> * All options will get the same name as in simplejson, only prefixed > with "json.". > * Exception: "json.assume_encoding" instead of "encoding", similar to > the Kid options, since "encoding" usually means the output encoding? > * Default values for the options the same as in simplejson? sounds good. > * Exception: ensure_ascii=False instead of True, this will make > non-enlgish json ouput much smaller and better readable? What exactly does ensure ascii do - I guess it produces \uXXXX literals? I *think* we might spare ourselves (or better others) a bit of trouble if using ensure_ascii=True - those who need to optimize size & readability should re-configure. Diez --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
