As mentioned earlier, I've created this site myself more or less from scratch. Here's an overview of the technologies used:

Language
Python. I've had previous blog implementations in PHP. I won't say I'm embarassed—we all need to start somewhere and PHP is a simple language. I originally went for a rewrite in Java using Spring (MVC) and Hibernate, but switched to Python after having used it for a small while at work. Python is more convenient in many ways, but I occasionally miss some of the "firmness" in Java.
Web framework
Pylons. I'll upgrade to 0.9.7 when I find the time. I haven't really looked at the changelog yet, but I like that they're moving away from star imports, at least related to the base controller. Star imports are ugly. Ever looked inside WebHelpers? *Shivers*
Templating language
Mako. I believe I'll change to Jinja2 after upgrading Pylons. We'll see. I like the inheritance blocks in Jinja better than the equivalent use of functions and function calls in Mako.
Web server
Apache 2 with mod_fcgid and flup.
Object-relational mapper
SQLAlchemy 0.4. But if you do an easy_install on it you currently get version 0.5.0 beta something. Why on earth are betas available by default? If a developer wants to use an unstable (by definition) version of a product, she should have to explicitly ask for it! Anyway...
Database engine
PostgreSQL for production and SQLite for development.
Authentication framework
Paste auth_tkt, customly wrapped for handling bad tickets. I just need something to handle the authentication cookies, and this does the job nicely.
Caching system
Memcached. I've put an abstraction layer on top of the Python Memcached client with anti-dogpiling. It's probably overkill by far on a site like this, but hey, it's fun!

The rest is just the object model, services, controllers, templates, styling, and configuration (including setting up virtual Python environments and creating deployment scripts) that makes it all into a functional web site. There are a few nifty solutions (if I might say so myself) in there which are candidate subjects for future posts.

I'm naturally keeping all code under version control. I started off with Subversion, which I've been using for quite a few years now, but have lately changed to Bazaar Version Control for this and another project, after pressure from a colleague to try it out. The only issue I have with Bazaar so far is the program name on the command line: bzr. I can't type it over and over again without straining my left arm, so I alias it to bvc (Bazaar Version Control). Have a look at your keyboard and compare b z r with b v c. The latter is obviously easier to type!

That's basically it. Don't hesitate to ask questions!