Source: prospector
Section: python
Priority: optional
Maintainer: Daniel Stender <debian@danielstender.com>
Uploaders:
 Python Applications Packaging Team <python-apps-team@lists.alioth.debian.org>
Build-Depends:
 debhelper (>= 9),
 dh-python,
 python (>= 2.7),
 python-setuptools,
 python-sphinx,
 pandoc,
 txt2man,
 python-nose,
 python-yaml,
 python-requirements-detector,
 python-setoptconf,
 pyflakes (>= 0.8.1),
 pylint (>= 1.4),
 python-pylint-common,
 python-pylint-celery,
 python-pylint-django,
 pep8 (>= 1.6.0),
 python-pep8-naming,
 pep257,
 python-mccabe,
 dodgy
Standards-Version: 3.9.6
Homepage: http://prospector.readthedocs.org/en/master/
Vcs-Svn: svn://anonscm.debian.org/python-apps/packages/prospector/trunk/
Vcs-Browser: http://anonscm.debian.org/viewvc/python-apps/packages/prospector/trunk/
Testsuite: autopkgtest

Package: prospector
Architecture: all
Depends:
 ${misc:Depends},
 ${python:Depends},
 ${sphinxdoc:Depends}
Description: comprehensive static Python code analyzer
 Prospector analyzes Python source files and puts out information about
 coding errors, potential problems, convention violation and unnecessary
 complexity.
 It provides an uniform and flexible interface for these tools:
  - Pylint (extensive Python code checker)
  - Pyflakes (checks Python code for logical errors)
  - Pep8 (checks for Python coding style conventions)
  - Pep8-naming (checks for naming conventions not covered by Pep8)
  - McCabe (checks for cyclomatic code complexity)
  - Pep257 (checks for compliance with the docstring conventions)
  - Dodgy (checks for hard coded passwords, VCS diff checkins etc.)
 .
 Prospector detects if code employs specific frameworks and libraries
 like currently Django (web application framework)
 and Celery (asynchronous task/job queue),
 and checks them by corresponding Pylint plugins.
 .
 Optionally, it also makes use of the analyzers Pyroma, Vulture, and Frosted
 (however, not yet completely available in Debian).
