> rather than disable it, why do you not use it? it's going to be there for a > long time, and although it is a bit tedious to enable it, it is worth doing > once and for all - remember that this is practically the only security hole > found in django after nearly 5 years of release.
I guess we will slowly move in this direction, but for now I just would like to upgrade our project to 1.2, because it has some feature we would like use. -- Filip Gruszczyński -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
