Revert "List Django as a dependency. Fix #96"

This reverts commit 9b520e9.

Apparently this is causing more problems than it solves, see:
#132

Author: atodorov

Diff for: README.md

@@ -10,33 +10,19 @@ pylint-django
 
 `pylint-django` is a [Pylint](http://pylint.org) plugin for improving code analysis for when analysing code using Django. It is also used by the [Prospector](https://github.com/landscapeio/prospector) tool.
 
-# Installation
+## Usage
 
-```
-pip install pylint-django
-```
-
-**WARNING:** `pylint-django` requires `Django` to be installed. Our `setup.py` file doesn't
-specify which particular version of Django is going to be installed because we have no idea
-what version is used inside your project. The latest version of Django will be installed if
-it has not been installed beforehand! DO NOT report issues about mismatching Django versions
-if that happens. Instead get your testing environment sorted out and make sure that you have
-the appropriate version of Django installed!
-
-# Usage
-
-## Pylint
+#### Pylint
 
-Ensure `pylint-django` is installed and on your path and then execute:
+Ensure `pylint-django` is installed and on your path (`pip install pylint-django`), and then run pylint:
 
 ```
 pylint --load-plugins pylint_django [..other options..]
 ```
 
-## Prospector
+#### Prospector
 
-If you have `prospector` installed, then `pylint-django` will already be installed as a dependency,
-and will be activated automatically if Django is detected.
+If you have `prospector` installed, then `pylint-django` will already be installed as a dependency, and will be activated automatically if Django is detected.
 
 ```
 prospector [..other options..]
@@ -56,14 +42,14 @@ Please feel free to add your name to the `CONTRIBUTORS.md` file if you want to b
 credited when pull requests get merged. You can also add to the `CHANGELOG.md` file
 if you wish, although I'll also do that when merging if not.
 
-# Tests
+## Tests
 
 The structure of the test package follows that from pylint itself.
 
 It is fairly simple: create a module starting with `func_` followed by
 a test name, and insert into it some code. The tests will run pylint
-against these modules. If the idea is that no messages now occur, then
-that is fine, just check to see if it works by running `scripts/test.sh`.
+ against these modules. If the idea is that no messages now occur, then
+ that is fine, just check to see if it works by running `scripts/test.sh`.
 
 Ideally, add some pylint error suppression messages to the file to prevent
 spurious warnings, since these are all tiny little modules not designed to
@@ -78,4 +64,4 @@ These are useful to quickly add "expected messages".
 
 # License
 
-`pylint-django` is available under the GPLv2 license.
+`pylint-django` is available under the GPLv2 license.

Diff for: setup.py

@@ -18,7 +18,6 @@
     install_requires=[
         'pylint-plugin-utils>=0.2.1',
         'pylint>=1.8.2',
-        'Django',
     ],
     license='GPLv2',
     classifiers=[