the occasional occurrence

Tomorrow Today (Tuesday the 28th) we are having a little online get together regarding the future of CherryPy.
A brief history of the last year
A lot has happened with CherryPy and the rest of the Python web development world in the last year. Things are continuing to progress quickly. For a little [...]

I have been wanting to update the look of my series of sites for a while. The revamp has begun with my home page.
Now I just need to integrate the look into my projects site and this here blog.
*Edit*
The blog is coming along…
cw

Well, the news is fairly public now. My family and I are moving from Illinois back to Ohio this summer. The gravitational pull of the grandparents on Curtis (my two year-old) alone was almost too much to resist. With the birth of Eli in December, it has become irresistable, since we want [...]

Over the past few months, CherryPy has taken a bit of flack for the way its WSGI support has been implemented. With the explosion in popularity of TurboGears, people started wanting to do things with CherryPy that hadn’t yet been perfected. There was some valid critcism raised against CP, and some good changes [...]

I read a couple blog entries in the past week about the Python interactive interpreter and how great it is. I have always found the interactive interpreter extremely useful, not to mention downright fun to mess around with. It is truly one of the really neat features of Python.
Reading those entries reminded me [...]

So what best practices should one follow when planning for the configuration of a redistributable CherryPy 2.2 application? That’s not a rhetorical question. I’m hoping to get a bit of brain dumping here from those of you in the CP community that will hopefully make its way into some official documentation.
In [...]

I have been thinking lately about how it is still pretty involved to deploy a CherryPy (or any Python web) application to a “production” server (Apache, lighttpd, IIS, etc).
The easiest method that I know at this point is mod_proxy with Apache:

<Virtualhost *>
ServerName cpsite.server.domain
[...]

I finally get it. I feel somewhat hip to WSGI.

A big thanks to Ben Bangert and his article WSGI and WSGI Middleware is Easy, which I like to call WSGI for Dummies

Anyhow, now that I “get it”, I have been messing with WSGI a bit. (read more)

Buffet 0.9 has been released.

This release includes a template composition feature provided by Bill Mill. In his words:

It would be nice to have a way to tell buffet to render multiple templates in sequence. For example, “return [(head, {}), (story, {}), (foot, {})]” Would render those three templates in order.

He provided a patch to support that feature, and it is now available for others to use. I love open source.

So … Buffet is at 0.9 now … it basically does everything that I originally intended for it to do (and more now). I have received lots of great feedback via email, on #cherrypy and in various mailing lists (thanks to all of you). So what’s going to make it 1.0?

Tests and profiling.

For both of those, I plan on making use of Robert Brewer’s excellent work in CherryPy. His test stuff is great. I have written a couple tests for CherryPy and it was pretty straight forward. For profiling, I am going to use CherryPy’s integrated profiler, but I am going to have to figure out how to profile a filter with it.

Anyhow, this is fun. Python is fun. CherryPy is fun. I have been making use of open source software for years now and it is cool to give back, even in a small way.

cw

It’s late now, and I’m tired, but I have released Buffet 0.6 (original release announcement). The major change in this release is that Buffet no longer depends on the builtin template “adapters” included in previous versions. Kevin from TurboGears and I worked out a common templating engine plugin format that both of our projects can share (and since they are not tied to Buffet, TG or CherryPy, other projects can use the plugins as well).