> My reasoning behind this is two-fold: > > first: I personally prefer to have explicit imports of what I want. > But I am aware that this reasoning is a personal preference and can > vary from one person to another. > > second: when you are new to python (and even when you are not) it is > easier to read some code and to say: "aah! the StringCol comes from > the sqlobject module", than to wonder: "ergh! from which import * > does this come from ?" > > I think the explicit import makes code easier to read. > When I first started using TG I had a hard time figuring out from > which import * came each item in the quickstarted controller/model.
This is a really good point. IMHO we need a consistent importing scheme for all docs, whatever the decision is. Right now it's all over the map between the docs and the book and the tutorials. A recommended scheme that all doc examples follow will make it much easier for new python programmers to copy and paste stuff while they are figuring things out. To experienced users we look at that right away when we get a name not defined error, but I know when I was first learning python it was constant tripping point. Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to turbogears-trunk@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
