On Dec 18, 2007 12:26 AM, Ben Bangert <[EMAIL PROTECTED]> wrote: > I'm also looking at some of the locations for things, and since beaker > handles its own stacked object proxy, I'm thinking it might be cleaner > and less confusing if projects imported the session object from where > the package that provides it... beaker. So instead of: > > from pylons import session > > 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." -- 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 -~----------~----~----~----~------~----~------~--~---
