> I wanted to see what people think about changing this way... it may > seem minor, but it's a stylistic change that would appear in docs, > quickstart, etc. And we don't have to do from turbogears import *. It > could be from turbogears import expose, vaildate, ...
It's a stylistic issue, so everyone must have an opinion, so here's mine: I think from turbogears import * is bad style because you can't see just by looking at the function name from where the function comes from. @turbogears.expose(template=...) def index(...) is much clearear than @expose(template=...) def index(...) Which leaves you guessing on what expose() it is. cherrypy.expose()? I'd prefer if the module names was a little shorter instead: @gears.expose(template=....) My personal preferences is to use "import modulename" when modulename contains mostly functions and "from modulename import someclass, someotherclass" when I want to use classes from modulename. Just my two cents, I can't say my style is better than anyone elses. -- mvh Björn
