Better attack handling on Apache(wsgi)/Django servers

I'm starting a new project on Django 1.0/Pinax and I'm noticing that these silly IIS attacks that I used to see in my previous logs show up in a much more cluttered way through Apache(wsgi)/Django. Is there a best practices way to handle these types of attacks so that the attack is logged (or not

Re: Django 1.0 for brand new site

Based on some internal responses and this one, I think I'll choose Ubuntu over Debian. This will be a shell only machine since I'm running it on Amazon. Anybody have thoughts on me not using Ubuntu? Let's say Debian Lenny? I only ask here because I'm trying to stay with the pack on a standard D

Django 1.0 for brand new site

Django users will be glad to know that I've pretty much decided to use Python/Django for a new site I'm creating. I was getting sick of PHP and I'm not convinced that Ruby (Rails/Merb) is robust enough for my tastes, so I've ended up here. Still, I'm now wondering if anybody has thoughts on whet