| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
In order to write this documentation, we need to also add documentation
for the --max-complexity option which was heretofore undocumented.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
And add a release note to document the change.
|
| | |
|
| |
|
|
|
|
|
| |
Upgrade version constraints on PyFlakes to only the versions that handle
Python 3.6
Closes #290
|
| | |
|
| |
|
|
|
|
|
|
| |
Instead of displaying the path to the temporary directory, as we always
have, it's been requested that we instead display the path to the file
that was copied to the temporary directory.
Closes #244
|
| |
|
|
|
|
|
|
|
|
|
| |
This adds two new methods to the BaseFormatter class:
- beginning
- finished
These will indicate when Flake8 begins and finishes processing a file.
Closes #251
|
| | |
|
| |
|
|
|
|
|
|
| |
Some PyFlakes messages weren't covered by unique messages, making them
impossible to select/ignore. This is now fixed.
To ensure we don't regress in the future, a test has been added that fails if
there's any uncovered messages.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we added support so users can do:
$ flake8 bin/executable
But this broke the fact that git hooks shouldn't check things like
reStructuredText doc files. This commit restores that functionality but
will cause bin/executable to be ignored in the git hook. This seems fair
since folks can amend their filename patterns to include it explicitly.
Closes #268
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
When we refactored our decision process to fix #239, we broke a subtle
corner case where extensions that are not off-by-default are to be
reported.
This further refactors that logic and adds specific tests around it to
ensure it works as expected and doesn't regress.
Closes #257
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Bump the version string as well
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Create sub-sections for different release series
When looking at the documentation, the release notes section on the
sidebar was incredibly long, due to the number of releases available.
To make this more usable, I've split the release notes index into
sections for each release series (e.g., 3.x, 2.x, etc.). This allows
documentation users to open the release notes sidebar section, and then
select which series they want. That will expand and let them pick the
version.
See merge request !145
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When looking at the documentation, the release notes section on the
sidebar was incredibly long, due to the number of releases available.
To make this more usable, I've split the release notes index into
sections for each release series (e.g., 3.x, 2.x, etc.). This allows
documentation users to open the release notes sidebar section, and then
select which series they want. That will expand and let them pick the
version.
|
| |/
|
|
|
|
|
| |
Document Flake8 for users expecting `man flake8` to work and include the
man page in Flake8's documentation.
Closes #247
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Add documentation for VCS hooks
Closes #249
See merge request !144
|
| | |
| |
| |
| | |
Closes #249
|
| |/
|
|
|
|
|
|
|
| |
This section of the docs could be read as pointing out the project as a
bad example. It was not intended this way, but I would like to avoid
anyone interpreting it this way. As a result, we'll continue to use
their configuration section as an example but not name names.
Closes #228
|
| | |
|
| |
|
|
|
|
|
|
| |
If we handle an exception, or early exit, or really anything, we should
exit non-zero (and we used to). This was a minor oversight.
Closes #209
Closes #248
|
| | |
|
| |
|
|
|
|
|
|
|
| |
When we rewrote Flake8 for 3.0, we unintentionally stopped forcibly
excluding some patterns regardless of what the user specified. This note
is added after the fact to make it easier for users to determine the
cause of any backwards incompatibility they might notice.
Closes #250
|
| |
|
|
|
|
|
|
| |
This attribute is introduced in pycodestyle 2.1.0
Closes #246
See: https://github.com/PyCQA/pycodestyle/issues/400
|
| | |
|
| |\
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Add --tee option to split report output stream.
The `--tee` option allows the linter report to be written to stdout, even
though it is being redirected to a file with the` --output-file` option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).
See merge request !90
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
The --tee option allows the linter report to be written to stdout, even
though it is being redirected to a file with the --output-file option.
This is useful if I want to store the report in a separate file for later
analysis but also be able to print the output on screen (e.g when running
in a CI environment).
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `tokens` property of the `FileProcessor` class only contains tokens of the
current line but not all tokens. So if a plugin which is only executed once
per file, that property is useless. To make the tokens also available to
plugins it is now be able to supply all the tokens of a file.
It also updates the documentation to separate which parameters are static and
which are changed on each line. Using the latter parameters on plugins which
are only run once per file isn't very sensible.
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
When invoked it will print out JSON that has all of the debugging
information needed by the maintainers to diagnose or reproduce a bug.
Closes #207
|
