From 98753710a7e58ce93b41d7ff426f2ef5040f9132 Mon Sep 17 00:00:00 2001 From: Russell Keith-Magee Date: Thu, 28 Oct 2010 12:36:51 +0000 Subject: [PATCH] Added documentation note for the backwards incompatible change in r13996. git-svn-id: http://code.djangoproject.com/svn/django/trunk@14387 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/releases/1.3.txt | 26 ++++++++++++++++++++++++++ 1 file changed, 26 insertions(+) diff --git a/docs/releases/1.3.txt b/docs/releases/1.3.txt index da4eaf993d..09f28b8203 100644 --- a/docs/releases/1.3.txt +++ b/docs/releases/1.3.txt @@ -183,6 +183,32 @@ command:: python manage.py sqlindexes sessions +No more naughty words +~~~~~~~~~~~~~~~~~~~~~ + +Django has historically provided (and enforced) a list of profanities. +The :doc:`comments app ` has enforced this +list of profanities, preventing people from submitting comments that +contained one of those profanities. + +Unfortunately, the technique used to implement this profanities list +was woefully naive, and prone to the `Scunthorpe problem`_. Fixing the +built in filter to fix this problem would require significant effort, +and since natural language processing isn't the normal domain of a web +framework, we have "fixed" the problem by making the list of +prohibited words an empty list. + +If you want to restore the old behavior, simply put a +``PROFANITIES_LIST`` setting in your settings file that includes the +words that you want to prohibit (see the `commit that implemented this +change`_ if you want to see the list of words that was historically +prohibited). However, if avoiding profanities is important to you, you +would be well advised to seek out a better, less naive approach to the +problem. + +.. _Scunthorpe problem: http://en.wikipedia.org/wiki/Scunthorpe_problem +.. _commit that implemented this change: http://code.djangoproject.com/changeset/13996 + .. _deprecated-features-1.3: Features deprecated in 1.3