| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
| |
Fixes issue #598. Had to modify some functional tests to ignore new message.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* this patch adds the basis of a new checker, 'async', which deals
with problems that can occur when working with async features added
in Python with PEP 492.
* We're also adding a new error, 'yield-inside-async-function', emitted on
Python 3.5 and upwards when the `yield` statement is found inside
a new coroutine function (PEP 492).
* Another new error is added, 'not-async-context-manager', emitted when
an async context manager block is used with an object which doesn't
support this protocol (PEP 492).
|
|
|
|
|
| |
This fixes a false positive related to abstract-class-instantiated.
Closes issue #648.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Using abbreviations for CLI options was never considered to be
a feature of pylint, this fact being only a side effect of using optparse.
As this was the case, using --load-plugin or other abbreviation
for --load-plugins never actually worked, while it also didn't raise
an error. Closes issue #424.
|
|
|
|
| |
Closes issue #639.
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The error is used when a bare raise is not used inside a try suite.
This can generate a RuntimeError in Python, if there are no active exceptions
to be reraised. While it works in Python 2 due to the fact that the exception
leaks outside of the except block, it's nevertheless a behaviour that
an user shouldn't depend upon, since it's not obvious to the reader of the code
what exception will be raised and it will not be compatible with Python 3 anyhow.
Closes issue #633.
|
| |
|
| |
|
|
|
|
|
|
|
| |
The reason behind this is that this kind of errors should be
detected by the type checker for *all* the builtins and not
as a special case for the reversed builtin. This will happen
shortly in the future.
|
|
|
|
| |
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.
|
| |
|