My preference would be for a name that doesn't conflict with any other names. Since there's a jsonify.py in TuroJson - even though this builds on it, it's still confusing. (Although an improvement over it being named json.py).
Maybe tgjson.py or tgjsonify.py or something similar? On Jan 8, 5:55 am, Christoph Zwerschke <[email protected]> wrote: > Am 08.01.2011 06:48 schrieb Sam: > > > Can we rename the json.py in the TG 1.5 skeleton as something else? > > I suggest jsonify, as this is a project specific extension of > turbojson.jsonify. Any objections? > > -- Christoph -- You received this message because you are subscribed to the Google Groups "TurboGears" 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?hl=en.
