Ahh I think I see what you're saying. It really isn't easy to develop
plugins per se for web.py, but it also isn't really that easy to
offload code in seperate modules (you have to hook and declare session
as part of web.ctx) I do see this as more of a mini-framework, because
there are things that you do end up having to figure out yourself, or
modifying part of the framework not to do dumb things (like start a
session/send a set-cookie header for every request, or have the db
clear out only stale un-authenticated sessions).
My point is, there's a lot of stuff you do end up having to figure out
for yourself, as the documentation is pretty spotty, and the results
will tell you a few different ways to do any one thing depending on
how old that particular revision. You really can't be afraid to get
your hands dirty if you want this framework to work they way you want,
and IMHO it needs more polishing. Something like django you would
never dream of messing with the internals, but what drove me to web.py
is the fact that it was way simpler to get something up and running.
Though some things do require expierementation, like running a WSGI
interface on both SSL and non-SSL ports, then adding debug interfaces
to manage it from there. I don't mind though, this is the sort of
thing I enjoy :), and I feel that's really in the spirit of Python in
general.
Ryan
On May 15, 2012, at 10:21 PM, Leandro Severino