Am 09.01.2011 22:55 schrieb Sam:
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).
I don't think we need/should construct module names different from all modules in other packages. That's what packages are good for, and all the different names for similar things will be confusing too. Keeping the same name makes it clearer that myproject.jsonify is intended to be simply an extension of turbojson.jsonify.
Note that we already have similar cases, e.g. myproject.controllers vs. turbogears.controllers, or myproject.tests vs. turbogears.tests, and this does not cause any problem either.
-- 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.
