| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
| |
These show that there were some subtle bugs in how we were matching
things and that there are bugs that need to be fixed.
|
| | |
|
| | |
|
| |
|
|
|
| |
This reverts commit ba2fb9c53a8316642249598f599bbf7608d54260, reversing
changes made to 63b91c95ea7795e3c3c90f2d643f685bfff312e9.
|
| |
|
| |
This reverts merge request !253
|
| |\
| |
| |
| |
| |
| |
| | |
Fix inconsistent newlines read from a file in python3
Closes #457
See merge request pycqa/flake8!253
|
| | | |
|
| |/
|
|
| |
Signed-off-by: Jintao Zhang <zhangjintao9020@gmail.com>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Refs #365
|
| |\
| |
| |
| |
| |
| |
| | |
Resolve "flake8 does not generate error when given a non-existent file on the command line"
Closes #405
See merge request pycqa/flake8!227
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
| |
This includes creating the pool, tearing it down under normal use, and
tearing it down in case of exception.
Doing this makes it harder to leak processes, as for instance was
happening in #410.
Fixes #410
|
| |
|
|
|
|
|
| |
In working on flake8-json, I noticed that setting newline was only
helpful for writing to an ouput-file but not to standard-out. It makes
sense for this setting to apply to both branches otherwise plugins need
to override the method to get the behaviour they expect.
|
| |\
| |
| |
| |
| |
| |
| | |
Add paths option in local-plugins config file.
Closes #379
See merge request pycqa/flake8!211
|
| | | |
|
| | | |
|
| |/ |
|
| | |
|
| | |
|
| |
|
|
|
| |
By slightly modifying our utility function to parse comma separated
lists we can parse local plugins similar to other configuration options.
|
| |
|
|
|
| |
This allows us to report whether or not a plugin is local when users
provide `flake8 --bug-report` output.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Closes #357
|
| |
|
|
|
|
|
| |
To match our new configuration file format and its allowance for spaces
in the list
Closes #356
|
| |
|
|
|
|
|
|
| |
Previously we were hitting the catch-all return that decided the error
was selected. Instead, let's add specific logic since we now know how we
would hit that and we actually don't want it to be selected.
Closes #354
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
This was mostly to prove to myself that we could possibly reach that
return more than actually covering that return. This just shows how
gnarly this logic actually is. I wish there were a better way to write
it.
|
| |
|
|
|
| |
Move all Violation related methods from the StyleGuide to our Violation
class.
|
| |
|
|
|
| |
Rename `decision_for` to `more_specific_decision_for` and
`should_report_error` to `decision_for`.
|
| |
|
|
|
| |
Convert it to test the DecisionEngine class directly and put them in
their own file.
|
| |
|
|
|
|
|
|
|
| |
In dealing with the decision logic in the StyleGuide recently I
recognized that the logic really doesn't belong strictly on the
StyleGuide. A separate object makes perfect sense especially from the
perspective of testability. This is a minor refactor intended solely to
facilitate further testing and perhaps making the logic easier to
understand for others.
|
| | |
|
| |\
| |
| |
| |
| |
| |
| | |
Further improve our handling of --select and --ignore
Closes #318
See merge request !187
|
| | |
| |
| |
| |
| | |
Add test to cover branch of decision logic we were not previously
exercising
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
There was a *very* subtle bug in how we handle blanket select statements
with error codes that are in our DEFAULT_IGNORE. In the specific case,
users were specifying ``--select E`` and E126 was not being properly
reported. This unveiled further logic bugs as we refined this.
Closes #318
|
| |/
|
|
|
|
|
|
|
|
| |
They are equivalent for iterating so remove the additional function
call.
Pattern identified as outdated by Lennart Regebro's PyCon 2017 talk
"Prehistoric Patterns in Python"
https://www.youtube.com/watch?v=V5-JH23Vk0I
|
| |
|
|
| |
Closes #329
|
| |
|
|
|
|
|
| |
When we parse out our comma separated lists, we should ignore empty
strings to avoid them breaking users' expectations.
Closes #330
|
| |
|
|
|
|
| |
* Use set literals instead of set([...])
* Avoid list(sorted(...)) as sorted returns a list
* Replace dict() with dict literal
|
| |
|
|
|
|
|
|
| |
By splitting out the logic to retrieve and return the formatting class
for an application, we can test it more easily and increase our test
coverage of this critical logic.
Refs #320
|