4 Feb 2006 04:00
[ANN] PyChecker 0.8.17 released
Neal Norwitz <nnorwitz <at> gmail.com>
2006-02-04 03:00:35 GMT
2006-02-04 03:00:35 GMT
A new version of PyChecker is available.
There are two notable new features (command line options):
--only and -#/--limit. --only will only print warnings from files
specified
on the command line. --limit will limit the number of warnings printed.
By default, only 10 warnings are printed unless you disable
the limit check: -# 0.
What is it?
PyChecker is a tool for finding bugs in Python source code.
It finds problems that are typically caught by a compiler for less
dynamic languages, like C and C++. It is similar to lint.
Comments, criticisms, new ideas, and other feedback is welcome.
Changes from 0.8.16 to 0.8.17:
* Fix spurious warning for Statement with no effect using bit shifts
* Add -#/--limit command line option to set the max # of warnings to show
* Remove broken command line options: -e/--errors, --complexity
* Add -e/--level command line options which allows the error level
to be specified: error, security, warning, unused, deprecated, style.
These names map to numbers: 90, 90, 70, 50, 40, 10 (error == security).
Specifying a value means all levels equal to or greater than it.
* Add --only option which displays warnings only for files specified
on the command line
* Add --evil option for users to prevent the interpreter from crashing
due to broken C extensions
* Fix wrong file name when warning about returning values from
__init__ functions. (#1291116)
* Fix a few more glitches with setup.py.
(Continue reading)
RSS Feed