On Tue, 2007-18-12 at 00:26 -0800, Ben Bangert wrote: > On Dec 18, 2007, at 12:12 AM, Ben Bangert wrote: > > In controllers, I think we can do away with the 'from ... import *'. > > While this works nicely for awhile, it almost always tends to leave > > a bad taste on people's mouth. The default controller template could > > instead come with the only necessary import: > > Of course, those wanting to use 'from ... import *', no reason they > can't continue to use that. ;)
Ditto for the names really, if people want to they can keep using c by aliasing it, right? I'm totally guilty of importing all the validators as v, because validator.String() never fits on a line in my widget. But it's a choice I make to obfuscate my own private code in return for screen real estate. I just dug into pylons recently for tg2, and I'm loving it. But, I will say that the more explicit you guys can make things to a new user the better, because it is the most difficult framework ( of tg, pylons, django ) to grok your code at first blush. ( Not that this is a bad thing ) I also believe that TG2 on pylons will be really beneficial to both communities, and the more so the easier it is to cross referrence docs and understand what's going on. So unified clear names with explicit imports will really help there. As would an agreed on standard practice for all how-tos and a big housekeeping there too! Iain --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-devel" 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/pylons-devel?hl=en -~----------~----~----~----~------~----~------~--~---
