No they're not the same. I'm developing a complex app based on Pyramid
and I love the fact that Pyramid is lightweight and not assuming things.
It allows me to:
1. choose peppercorn + colander to validate multilevel forms (forms that
are not flat key-value pairs but complex hierarchies), instead some flat
key-value form validation which I'd have to work around to implement this
2. reuse same colander schemes to validate model data coming from or to
channels other than POST (like daily XML and CVS imports / exports)
instead of duplicate work or have to work around and simulate POST if I
wanted to reuse the validation scheme
3. use my own authn/authz schemes to implement pure AJAX client
authentication, and while at it choose whatever persistence model I want
4. use SQLAlchemy for ORM and not some in-house concoction
5. use Mako templating or any other templating system, I just love Mako
6. write maintenance and command line scripts that bootstrap the
application so I can reuse its facilities without having to duplicate code
.oO V Oo.
On 12/12/2011 05:51 PM, rihad wrote:
Perhaps lightweight frameworks
such as Pyramid are for more advanced usage, although I doubt for
which purpose, given that problems a web programmer faces in his
projects are amazingly the same.
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" 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-discuss?hl=en.
