From dd551326433241f321fef9177e9487fef13348db Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Mon, 9 Jun 2014 11:53:09 -0400 Subject: [PATCH] Removed extras/csrf_migration_helper.py --- docs/ref/contrib/csrf.txt | 4 - extras/csrf_migration_helper.py | 356 -------------------------------- 2 files changed, 360 deletions(-) delete mode 100755 extras/csrf_migration_helper.py diff --git a/docs/ref/contrib/csrf.txt b/docs/ref/contrib/csrf.txt index 4c37f7448c..b1dd2a0ff0 100644 --- a/docs/ref/contrib/csrf.txt +++ b/docs/ref/contrib/csrf.txt @@ -72,10 +72,6 @@ To enable CSRF protection for your views, follow these steps: :func:`~django.shortcuts.render_to_response()` wrapper that takes care of this step for you. -The utility script ``extras/csrf_migration_helper.py`` (located in the Django -distribution, but not installed) can help to automate the finding of code and -templates that may need these steps. It contains full help on how to use it. - .. _csrf-ajax: AJAX diff --git a/extras/csrf_migration_helper.py b/extras/csrf_migration_helper.py deleted file mode 100755 index e7df65d056..0000000000 --- a/extras/csrf_migration_helper.py +++ /dev/null @@ -1,356 +0,0 @@ -#!/usr/bin/env python - -# This script aims to help developers locate forms and view code that needs to -# use the new CSRF protection in Django 1.2. It tries to find all the code that -# may need the steps described in the CSRF documentation. It does not modify -# any code directly, it merely attempts to locate it. Developers should be -# aware of its limitations, described below. -# -# For each template that contains at least one POST form, the following info is printed: -# -# -# AKA: -# POST forms: -# With token: -# Without token: -# -# -# Searching for: -#