| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
| |
Update release date as well
|
| |
|
|
|
|
|
| |
For our Legacy API users, StyleGuide.init_report should reset the
formatter attribute before calling Application.make_formatter().
Closes #200
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, all testing was done from the directory in which the
configuration file lived, so this bug went unnoticed. However, if you
run Flake8 against its own source from a directory above, you would
notice that the patterns in the exclude config value in tox.ini were
ignored. This is because we (like any reasonable person) are using
relative paths. The path is relative, however, to the directory in
which the configuration file was located. So we keep track of which
directory that is and use that to normalize the paths in the config
file.
Yes, there is an unrelated change to our tox.ini in this commit as
well. ;-)
Closes #194
|
| |
|
|
|
|
|
| |
This avoid overwriting portions of our log output when using Flake8
in verbose mode.
Closes #193
|
| | |
|
| |
|
|
|
|
|
|
| |
Due to https://bugs.python.org/issue27649, we cannot continue to
expect multiprocessing to work as we expect and document it on Windows.
As such, we are going to revert back to our previous behaviour of
disabling it across all versions of Python on Windows to provide the
default expected behaviour of Flake8 on that Operating System.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, to ensure that plugins on by default were reported, we
added them to the select list. This means that ignoring them became
impossible. To accomodate our reporting logic and a user's ability
to ignore, we need to keep our select and extended select lists
separated.
This allows us to have a better understanding of who is selecting what,
where, and how and make our decision as to whether or not an error
should be reported more wisely.
Closes #195
|
|
|
This makes the regular expression a bit more complex, and potentially
slower, but it will fix the issue where users had noqa comments with
colons followed by explanations.
Closes #178
|