Merge pull request #800 from jdufresne/nose

Remove suggestion and documentation of using unmaintained nose

CONTRIBUTING.rst

@@ -69,27 +69,19 @@ GitHub has an excellent `guide`_.
 The current tests are written in 2 styles:
 
 * standard xUnit based only on stdlib unittest
-  (can be executed with nose)
 * functional test using a custom framework and executed by the
   pycodestyle itself when installed in dev mode.
 
 
 Running unittest
 ~~~~~~~~~~~~~~~~
 
-While the tests are writted using stdlib `unittest` module, the existing
-test include unit, integration and functional tests.
+The tests are writted using stdlib `unittest` module, the existing test
+include unit, integration and functional tests.
 
-There are a couple of ways to run the tests::
+To run the tests::
 
     $ python setup.py test
-    $ # Use nose to run specific test
-    $ nosetests \
-    >    testsuite.test_blank_lines:TestBlankLinesDefault.test_initial_no_blank
-    $ # Use nose to run a subset and check coverage, and check the resulting
-    $ $ cover/pycodestyle_py.html in your browser
-    $ nosetests --with-coverage --cover-html -s testsuite.test_blank_lines
-
 
 Running functional
 ~~~~~~~~~~~~~~~~~~

docs/advanced.rst

@@ -25,9 +25,6 @@ in your project::
           self.assertEqual(result.total_errors, 0,
                            "Found code style errors (and warnings).")
 
-If you are using ``nosetests`` for running tests, remove ``quiet=True``
-since Nose suppresses stdout.
-
 There's also a shortcut for checking a single file::
 
   import pycodestyle

testsuite/support.py

@@ -215,7 +215,3 @@ def run_tests(style):
     if options.testsuite:
         init_tests(style)
     return style.check_files()
-
-
-# nose should not collect these functions
-init_tests.__test__ = run_tests.__test__ = False