10 comments

[ 2.8 ms ] story [ 37.1 ms ] thread
yawn
I'm a Django fan, but in defense of this guy this is a pretty insignificant thing to post to HN.
I have to agree that a routine update to security features hardly qualifies as front-page news. No wonder the Ruby guys think Python is no fun!
We should whip up some artificial controversy based on personality clashes between two or more immature community icons!
Cool, I've just started using Django so it's good to see it's still being developed.
Django seems to be a pretty active project, so I'm not sure what gave you the impression that it wasn't developed:

http://code.djangoproject.com/timeline

Looks like the 1.2.2 security release they did earlier this week was a bit rushed, partially because the security issue was reported via the public bug tracker instead of the security contact address.

Django is awesome and is really active. Go look at some records Sir.
(comment deleted)
(comment deleted)
It's a little worrying that the release is essentially just a fix for patch and package mistakes in 1.2.2. I know that 1.2.2 was a pretty urgent security update, but to re-update it a day later because the patch was broken and you botched the packaging just doesn't fill me with confidence.