| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
|
| |
The html reporter was lately a second class citizen in Pylint,
being underdeveloped and mostly neglected. It has a couple of bugs,
but the more important reason why this is removed is that we now have
a much better json reporter, which can be used as a basis for more
prettier html Pylint outputs.
Part of #975
|
| | |
|
| |
|
|
| |
with local namespace packages, such as no-name-in-module.
|
| |
|
|
| |
Currently 'pylint -E' disables all non-error messages, but this includes fatal errors as well. This change reverts that, since fatal errors are errors after all.
|
| |
|
|
| |
Close #486
|
| |
|
|
|
|
|
|
|
|
| |
This fixes an issue related to impredictible order of the disable / enable
elements from a config file. In certain cases, the disable was coming before
the enable which resulted in classes of errors to be enabled, even though the intention
was to disable them. The best example for this was in the context of running multiple
processes, each one of it having different enables / disables that affected the output.
Close #815
|
| |\
| |
| |
| |
| |
| | |
master now has become 2.0, there won't be another 1.6 anymore,
since the focus of the team is on the next big release now.
Minor bug fixes will be implemented though in 1.5.X.
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
As per discussion from issue #746, the reports were disabled by
default in order to simplify the interaction between the
tool and the users. The score is still shown by default,
as a way of closely measuring when it increases or decreases
due to changes brought to the code.
The patch introduces a new command line flag, "--score" or its
shorthand version, "-s", which controls if the score is shown or not.
By default, it's set to true.
|
| | | |
|
| | |
| |
| |
| | |
This is a step towards making pylint more sane, as per the discussion from issue #746.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This addresses issue #156 by allowing for multiple ignore patterns
to be specified. Rather than clobber the existing ignore option, I've
introduced a new one called ignore-patterns. That way there are as few
surprises as something involving regular expressions can have.
Multiple patterns must be separated by a comma. For example, if I
wanted to ignore all files that started with `test_` and `_`, I'd pass this
in: `--ignore-patterns="test_.*","_.*"`.
Close #156
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some reporters are aggregating the messages instead of displaying
them when they are available. The actual displaying was conflatted
in the generate_reports. Unfortunately this behaviour was flaky
and in the case of the JSON reporter, the messages weren't shown
at all if a file had syntax errors or if it was missing.
In order to fix this, the aggregated messages can now be
displayed with Reporter.display_message, while the reports are
displayed with display_reports.
Close #766 and #765
|
| |/ |
|
| | |
|
| |
|
|
| |
AstroidSyntaxError.
|
| | |
|
| | |
|
| |
|
|
| |
function.
|
| | |
|
| |
|
|
| |
Closes issue #632.
|
| |
|
|
|
|
|
|
| |
With this change, we moved away from depending on logilab-common,
having in Pylint all the components that were used from logilab-common.
The API should be considered an implementation detail and can change at
some point in the future.
Closes issue #621.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
into pylint.config
The reason behind this is that we can better control the behaviour
of the underlying configuration modules, such as the case for undefined
options or for quickly fixing other bugs. Another side effect of this
change is that it gets us closer to the moment where we will not
be dependent on logilab.common anymore, which will definitely
make our pytest users happy.
Some parts were copied almost verbatim from logilab.common.configuration
and logilab.common.optik_ext and pylint.config will definitely need
a refactoring and reengineering for abstracting the configuration,
so that we won't use optparse anymore, but that's subject for another
patch.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
--HG--
branch : no-logilab-common
|
| |
|
|
|
| |
--HG--
branch : no-logilab-common
|
| |
|
|
|
| |
--HG--
branch : no-logilab-common
|
| |
|
|
|
| |
We only need the version, and it's available directly in logilab.common.
Closes issue #575
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
related to a particular line.
|
| |
|
|
| |
This fixes #506.
|
| |\ |
|
| | | |
|
| | | |
|
| |/ |
|
| |
|
|
|
|
|
| |
The performance is improved by obtaining the files which should be analyzed
from the list of given modules, using PyLinter.expand_modules. This is already
what PyLinter._do_check does, but the behaviour was missing from PyLinter._parallel_check.
Closes issue #479.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The option ``--optimize-ast`` will control the peephole optimizer,
which is used to optimize a couple of AST subtrees. The current problem
solved by the peephole optimizer is when multiple joined strings,
with the addition operator, are encountered. If the numbers of such
strings is high enough, Pylint will then fail with a maximum recursion
depth exceeded error, due to its visitor architecture. The peephole
just transforms such calls, if it can, into the final resulting string
and this exhibit a problem, because the visit_binop method stops being
called (in the optimized AST it will be a Const node).
|
| |
|
|
| |
msg-template instead. Closes issue #215.
|
| |\
| |
| |
| | |
#422 [pylint sprint] Create pylintrc and disable checking for all issues
|
