On Tue, 2007-01-23 at 11:23 -0500, Karl Guertin wrote:
> On 1/23/07, Peter Russell <[EMAIL PROTECTED]> wrote:
> > I'd be interested in knowing what you dislike about CherryPy, I've been
> > using it quite a lot recently, and found it to be very transparent, and
> > well documented - to the point I almost wonder why they felt the need
> > for a new version!
> 
> CP3 is faster and is WSGIfied!
> 
> > I'm prejudiced against Paste, partly because I don't really get what it
> > is, and partly because the parts of Turbogears that seem to give me the
> > most headaches (SQLObject and Formencode) have websites with the same
> > templates as the Paste website :-)
> 
> To make a simplifying analogy, WSGI serves the same purpose in web
> frameworks as Buffet does in templating. It allows the possibility of
> mixing and matching components across different packages. Paste
> provides a set of tools for gluing WSGI components together. The
> websites use the same templates because the projects were all
> started/written by Ian Bicking.
> 
> If you took CherryPy 2, exploded it into it's atomic components and
> wired them back together with Paste, you'd basically have the pieces
> of Pylons that differ from TG. CP3 is similar in concept, but it's not
> wired together using Paste. I'm glossing over some details, but that's
> the basic idea.

And is the end result as good as CherryPy?  I was surprised to hear Bob
say he didn't like CherryPy, because I thought it was a good example of
a project that was complete in it's domain, and easy to use and
understand, whilst powerful.  It's clearly (to me) very well thought
out.  I've been able to do a lot with CherryPy without having to read
the source code (try that with Turbogears widgets, SQLObject or
FormEncode!), and where I have (only ever trying to debug errors I've
made myself) I've found it very transparent, I've looked at one or two
functions without having to internalise whole modules.  

There are a lot of bits of a standard TurboGears that I have issues with
(mostly the bits that are being replaced: SQLObject, Kid, Widgets).
CherryPy isn't one of them.

> 
> > You've just led me to discover this in TurboGears.  I've been
> > complaining that interactive debugging of turbogears is too hard for
> > ages, and I had no idea this existed.  Thanks!
> 
> It's turned off by default because it allows remote code evaluation.

Yeah, that's understandable.  Still it is sweet and a great example of
what WSGI can do for us :-)

> 
> > 
-- 
Peter Russell <[EMAIL PROTECTED]>
Qustom


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears" 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/turbogears?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to