| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
| |
required-attributes, is slated for removal in Pylint 1.6.
|
| |
|
|
|
|
|
|
| |
The reason behind this removal is the fact that it's a specialized
flag and there are solutions for the original problem:
use --generated-members with the members that causes problems
when using Zope or add AST transforms tailored to the zope
project. Closes issue #570.
|
| |
|
|
|
| |
The error is emitted when the `continue` keyword is found
inside a `finally` clause, which is a SyntaxError.
|
| | |
|
| |
|
|
| |
--disable option. Closes issue #608.
|
| | |
|
| |
|
|
| |
Closes issue #604.
|
| |
|
|
|
|
|
| |
missing modules with a relative import from a package.
The change improves how relative imports are shown when they are missing,
with the absolute name, instead of the relative one.
|
| |
|
|
|
|
| |
ignored-classes.
Thanks to The-Compiler for noticing the discrepancy.
|
| |
|
|
|
|
| |
patterns.
Closes issues #244 and #297.
|
| |
|
|
|
|
| |
This error is emitted when a name is found to be both nonlocal and global in the same scope.
This is a SyntaxError in Python 2, but Python 3's ast happily parses it, so it needs
to be a separate error. Closes issue #581.
|
| | |
|
| |
|
|
|
|
| |
We moved pyreverse.inspector.Project, pyreverse.inspector.project_from_files
and pyreverse.inspector.interfaces. These were moved since they didn't belong in astroid
and they can be better maintained inside pyreverse itself.
|
| |
|
|
|
|
|
|
| |
Unfortunately, this warning exhibits currently way too many false
positives, practically rendering this error useless. I can't fix
all of them until I release Pylint 1.5, so the most reasonable
choice for now is to disable it and reenable it as soon as we fix
those problems.
|
| |
|
|
|
|
| |
This error is emitted when two a binary arithmetic operation is
executed between two objects which don't support it
(a number plus a string for instance).
|
| |
|
|
|
|
| |
This error is emitted on Python 3 when a Starred expression (*x) is
not used in an assignment target. This is not caught when parsing the
AST on Python 3, so it needs to be a separate check.
|
| |
|
|
|
|
| |
This error is used when a star import is detected in another scope than the
module level, which is an error on Python 3. Using this will emit a
SyntaxWarning on Python 2.
|
| |
|
|
| |
and memoryview, which weren't detected until now).
|
| |
|
|
|
| |
This error is emitted when a starred expression (*x) is used as the lhs
side of an assignment, as in `*x = [1, 2]`. This is not a SyntaxError on Python 3 though.
|
| |
|
|
|
| |
The error is emitted when there are more than one starred expression (*x) in an assignment.
The warning is emitted only on Python 3.
|
| | |
|
| |
|
|
| |
returns YES from inference).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This patch improves the way how arguments-differ understands the differences
between classmethods, staticmethods and properties. Closes issue #548.
|
| |
|
|
|
|
|
| |
This new error is emitted when an unary operand is used on
something which doesn't support that operation (for instance,
using the unary bitwise inversion operator on an instance which
doesn't implement __invert__).
|
| |
|
|
| |
the current folder.
|
| |
|
|
|
|
| |
We don't know what those bases actually are and it's better
to assume that the user knows what he is doing rather than emitting
a message which can be considered a false positive.
|
| |
|
|
|
|
| |
This new warning is emitted when a conditional statement (If, IfExp) uses a test
which is always constant, such as numbers, classes, functions etc.
This is most likely an error from the user's part. Closes issue #524.
|
| | |
|
| |
|
|
| |
Exception or bare except clause.
|
| | |
|
| |
|
|
| |
bare except handlers.
|
| | |
|
| |
|
|
| |
'unexpected-special-method-signature'.
|
| |
|
|
|
| |
This is emitted when a special method (dunder method) doesn't have the expected signature,
which can lead to actual errors in the application code. Closes issue #253.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This patch involves a lot of subtle changes:
* is_defined_before takes in consideration the fact that its argument
node is a default value for a Lambda / Function.
If it is a default value, then the search is left to the parent of
the lambda. Basically for x in the following, the result of is_defined_before
will be determined by foo:
def foo():
x = 42
func = lambda x=x: x * x
return func
* there's another special rule for undefined-variable which verifies that
a node is used in Arguments.defaults and if the actual definition
is happening before the Arguments statement, basically trying
to understand the following:
class A:
x = 42
foo = lambda x=x: x * x
* undefined variable is emitted if both scope types, for the node
analyzed and for its actual definition, is they are both lambda
scopes.
Closes issue #404.
|
| |
|
|
|
|
|
| |
This patch improves the detection of undefined variables and variables used before
assignment for variables used as default arguments to function,
where the variable was first defined in the class scope.
Closes issue #342.
|
| |
|
|
|
|
|
|
| |
access-member-before-definition for mixin classes.
Actual errors can occur in mixin classes, but this is controlled by the ignore-mixin-members option,
so if something is a legitimate error, then the user can pass --ignore-mixin-members=no
in order to check these in mixin classes as well. Closes issue #412.
|
| |
|
|
|
|
|
|
|
|
| |
Detect undefined variable cases, where the "definition" of an undefined
variable was in del statement, e.g:
x = y
del y
Instead of emitting used-before-assignment, which is totally misleading,
it now emits undefined-variable. Closes issue #528.
|
| |\
| |
| |
| | |
New extensions directory, new optional checker of Sphinx style, Google style and Numpy style parameter documentation
|
| | | |
|
| | | |
|
| | |\ |
|
| | | |\ |
|
| | | |\ \ |
|
| | | | |\ \ |
|
| | | | | |\ \
| | | | | | |
| | | | | | |
| | | | | | | |
file doc/extensions.rst
|
| | | | | | | | |
|
