Looks like pylons is helping to make the decision for us: http://pylonshq.com/project/pylonshq/changeset/2058%3A45f1838d28a5
c and g are going away in the next version of Pylons, so we should be forward compatible ;) On Tue, Mar 3, 2009 at 8:16 PM, Chris Miles <[email protected]> wrote: > > > On 04/03/2009, at 6:06 AM, Christoph Zwerschke wrote: > > > > > Mark Ramm schrieb: > >> Well, we're not exporting any of the on letter variables, and I don't > >> like 1 letter variables generally. But I'll not fight about it if > >> there's concensus that we should export them. > > > > We need to do something anyway: It makes no sense that tg.__init__ > > imports g from pylons and puts an undefined "app_globals" in __all__. > > > > Currently you can "from tg import g", but not "from tg import > > app_globals". On the other hand you can "from tg import tmpl_context" > > but you can't "from tg import h". We must decide to either promote all > > the one-letter names or all the longer names - or both variants. > > My preference would be to export only the full names and let the user > alias them to one letter names if that's what they prefer (which may > become common practice, but isn't forced), > > from tg import app_globals as g > from tg import tmpl_context as c > > Cheers, > Chris Miles > > > > > -- Mark Ramm-Christensen email: mark at compoundthinking dot com blog: www.compoundthinking.com/blog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" 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-trunk?hl=en -~----------~----~----~----~------~----~------~--~---
