On Dec 18, 2007 12:12 AM, Ben Bangert <[EMAIL PROTECTED]> wrote:
> After talking with Ian Bicking a bit tonight, I'm finally fully sold
> on retiring the one-letter variable names from Pylons. The most likely
> replacement names:
> c -> context
> g -> ??? (as globals/global is already taken)
> h -> GONE (import the modules you need, most ppl want similar
> functions and can't find them anyways, importing them teaches people
> where they are, and shows them what else they might want to use)

Shock and minor grumble, but more curiosity.  I know the one-letter
globals are not popular in some quarters as being obscure and
Myghtyisms, but what are your main reasons for dropping them?

If we're going to make 'c' so inconcise it's cumbersome, should we go
all the way and switch to dict/@expose as the default?

Can we make these 'self' attributes in the controller so as to
minimize the use of StackedObjectProxiees?

self.request
self.pylons.request
self.pylons.config

See, it has a nice ring to it.  The shorter names would be more
convenient, but the 'pylons' attribute would minimize collisions with
controller action names.

> The default controller template could
> instead come with the only necessary import:
>
> from yourprojb.lib.base import BaseController

I would leave the logging line in place though, to encourage ppl to
use it and to make the lack of 'print' less burdensome.

> PS: So sorry Mike and James and anyone else working on the book, but I
> think this will really help, hopefully just a global search/replace in
> the text? :)

James is the only one working on the book right now.  I won't have any
drafts to review until he's finished.  Poke him a bit to make sure
he's aware of the changes, he kind of goes on hermit trips for
periods.

-- 
Mike Orr <[EMAIL PROTECTED]>

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to