From edd767d2612d891a906268cf590571f541dd164f Mon Sep 17 00:00:00 2001
From: Adrian Holovaty <adrian@holovaty.com>
Date: Thu, 7 Oct 2010 15:13:00 +0000
Subject: [PATCH] Set default PROFANITIES_LIST setting to an empty tuple. This
 is technically backwards-compatible if you rely on a Web framework providing
 you with a woefully incomplete list of naughty words. Fixes #8794

git-svn-id: http://code.djangoproject.com/svn/django/trunk@13996 bcc190cf-cafb-0310-a4f2-bffc1f526a37
---
 django/conf/global_settings.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/django/conf/global_settings.py b/django/conf/global_settings.py
index cd85ce0641..db0110e472 100644
--- a/django/conf/global_settings.py
+++ b/django/conf/global_settings.py
@@ -439,7 +439,7 @@ COMMENTS_ALLOW_PROFANITIES = False
 
 # The profanities that will trigger a validation error in the
 # 'hasNoProfanities' validator. All of these should be in lowercase.
-PROFANITIES_LIST = ('asshat', 'asshead', 'asshole', 'cunt', 'fuck', 'gook', 'nigger', 'shit')
+PROFANITIES_LIST = ()
 
 # The group ID that designates which users are banned.
 # Set to None if you're not using it.