[Checkins] SVN: z3c.dependencychecker/trunk/src/z3c/dependencychecker/USAGE.txt Removed introduction that's now in the main README

[Reinout van Rees]

Log message for revision 106373:
  Removed introduction that's now in the main README
  

Changed:
  U   z3c.dependencychecker/trunk/src/z3c/dependencychecker/USAGE.txt

-=-
Modified: z3c.dependencychecker/trunk/src/z3c/dependencychecker/USAGE.txt
===================================================================
--- z3c.dependencychecker/trunk/src/z3c/dependencychecker/USAGE.txt	2009-12-10 10:57:24 UTC (rev 106372)
+++ z3c.dependencychecker/trunk/src/z3c/dependencychecker/USAGE.txt	2009-12-10 10:58:09 UTC (rev 106373)
@@ -63,26 +63,3 @@
     setup.py to have effect.
     <BLANKLINE>
 
-So z3c.dependencychecker reports on:
-
-- **Unused imports**: pyflakes is another tool that does this (and that also
-  reports on missing variables inside the files).
-
-- **Missing (test) requirements**: imports without a corresponding requirement
-  in the ``setup.py``.  There might be false alarms, but at least you've got a
-  (hopefully short) list of items to check.
-
-  Watch out for packages that have a different name than how they're imported.
-  For instance a requirement on ``pydns`` which is used as ``import DNS`` in
-  your code: pydns and DNS lead to separate "missing requirements: DNS" and
-  "unneeded requirements: pydns" warnings.
-
-- **Unneeded (test) requirements**: requirements in your setup.py that aren't
-  imported anywhere in your code.  You *might* need them because not
-  everything needs to be imported.  It at least gives you a much smaller list
-  to check by hand.
-
-  If something is only imported in a test file, it shouldn't be in the generic
-  defaults.  Currently you don't get a separate list of requirements that
-  should be moved from the regular to the test requirements.
-