On Tue, Dec 18, 2007 at 01:07:50AM -0800, Mike Orr wrote: > > 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."
+1 on that. Please provide the "session" by default. Pylons may be re-using other components but IMHO that should be hidden from the user. It's bad enough that I have to copy the "SQLAlchemy in a hurry" article for every project. I wouldn't mind if Pylons came with a tighter integration of SQLAlchemy just like we had with pylons.database. And be it that the "in a hurry" setup is put into model/__init__.py and commented out by default. Not cluttering the namespace with "import *" is probably a good idea. But I'd have to get used to writing "content" which is way longer - I'm not sure that really helps. I better not count the occurences of "c." in my projects. :) Cheers Christoph --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
