On Dec 18, 2007, at 1:44 AM, Christoph Haas wrote:
+1 on that. Please provide the "session" by default. Pylons may bere-using other components but IMHO that should be hidden from the user.
Yea, the thing is, it isn't really re-using the other components, its just putting their WSGI app in your project, and *your* using it. So it makes some sense that you'd import from the library you're using.
It's bad enough that I have to copy the "SQLAlchemy in a hurry" articlefor 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 andcommented out by default.
True, I'm considering having that in the template and commented out as well. It's the default recommendation, and all the rest of our defaults are in the templates... it would make sense to have that there too.
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'mnot sure that really helps. I better not count the occurences of "c." in my projects. :)
No reason you can't import context as c. ;) Cheers, Ben
smime.p7s
Description: S/MIME cryptographic signature