-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Optimize handling of long lines for checkers like 'missing-final-newline' #5925
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
for more information, see https://pre-commit.ci
Pull Request Test Coverage Report for Build 1992225427
💛 - Coveralls |
CI seems to be broken for the main branch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @skirpichev, I got caught up in other things and haven't had the time to look at this.
Some minor changes to the comments and structure of the pattern. We might be able to sneak this in 2.13
👍
Edit: Btw, CI should pass again as I merged the PR that fixed it.
Ok, tests pass and, I hope, I don't forget anything from the requested changes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @skirpichev for you work and the quick responses to my review! LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you ! And congratulation on becoming a pylint contributor :)
BTW, there are two context managers to handle timeouts (in tests/checkers/unittest_refactoring.py and in tests/test_regr.py). Probably, one from definitions could be reused (if you don't like pytest-timeout). |
Nice catch ! I have nothing against using external pytest plugins. They probably did not exist when the context manager were first created. |
Yeah, I need to move those to |
On Thu, Mar 17, 2022 at 01:02:40AM -0700, Daniël van Noord wrote:
Yeah, I need to move those to conftest. It's on my (long) todo list 😄 Feel
free to open a PR to do so!
I would suggest using pytest-timeout instead. Any objections?
|
None, other than that I haven't worked with it before so when I first made a "timeout test" myself for |
CONTRIBUTORS.txt
if you are a new contributor.doc/whatsnew/<current release.rst>
.Type of Changes
Description
A replacement for #5786 per suggestion of @DanielNoord. Fix catastrophic backtracking in OPTION_RGX.
Closes #5724