Mike Orr wrote:
>> When you want sessions, you'd add: from beaker.middleware import
>> beaker_session as session
>
> Ugh, you really expect people to want to memorize this? Sessions
> are supposed to be built into megaframeworks, not require some
> obscure import. "I think I'll just use Rails instead; it's more
> straightforward."
I actually agree with Mike on this point. At some level, Pylons is in
fact a framework, and providing structure for the user is a good thing
for a framework to do. It'd be nice, if at the top of my controllers I
could do this:
from pylons import request, response
from pylons import context, app_globals, session
Clear, and to the point. I understand that importing from beaker is
more "explicit" it also makes Pylons seem a bit less cohesive, and more
like a bunch of parts glued together.
--
Jonathan LaCour
http://cleverdevil.org
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pylons-devel" group.
To post to this group, send email to pylons-devel@googlegroups.com
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
-~----------~----~----~----~------~----~------~--~---
