Comments on: Half-baked CherryPy

By: poppedcherry

poppedcherry — Tue, 30 Nov 1999 00:00:00 +0000

Yeah, CherryPy looks great at first… until you try something slightly complex with it, and end up having to run everything through default() so it can handle forms with lots of inputs, and manually handle redirects, cookies, sessions (something like “warning: this isn’t thread safe”), etc… Some things it might handle but with a lack of documentation it’s faster to do it yourself. CherryTemplate has various glitches (e.g. filling in template values with old data if you left any variables out, which could expose user A’s data to user B; not handling start and end tags well; near-useless error messages when it can’t parse things). The python-hosting site, done with CherryPy, is very simple. The CherryPy site is actually a Trac site. What’s that about eating your own dog food..?

By: projecktzero

projecktzero — Tue, 30 Nov 1999 00:00:00 +0000

Give me a break! Plenty of sites don't "eat their own dog food". Not because their software is bad, but because some other software was more convenient or focused on the specific need. Why should you build something from scratch when there are plenty of ready-made solutions already out there?(wikis, forums, project tracking...)

Besides, the CherryPy site has testimonials and success stories that demonstrate the usefulness of CherryPy.

http://www.cherrypy.org/wiki/CherryPyUserTestimonials http://www.cherrypy.org/wiki/CherryPySuccessStory

By: Jason

Jason — Tue, 30 Nov 1999 00:00:00 +0000

Why not just use Django?

By: Jeff Watkins

Jeff Watkins — Tue, 30 Nov 1999 00:00:00 +0000

Jason, I don't know. Some of the ORM code in Django looks a little weird to me. But I don't doubt it works, just it feels a little uncomfortable.

Mind you, given my discomfort with SQLObject, I'm not certain whether Django would be better or worse.

I'm in the process of coming up with a new platform for my Web site here, so maybe I'll give Django a look.