Skip to content
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

Fix bug for plugins using extend_default_ignore #1317

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

sigmavirus24
Copy link
Member

Since Flake8 3.0 we've had the ability for plugins to use
extend_default_ignore to register codes they want disabled by default.
This, however, was a permanent disabling unfortunately. Our code didn't
have a way of understanding that this new set of ignore codes was
actually the 'default' set for that run. Much like the
extended_select_list, we now attach extended_ignore_list to be able to
confidently determine if the ignore we get in the DecisionEngine is
actually the Default Ignore list and what plugins what us to ignore by
default.

Refs PyCQA/pep8-naming#157


Extra entertainment for Anthony
Screenshot-2021-04-15T09:16:52

Copy link
Member

@asottile asottile left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lg2m! thanks for reformatting the tests, that was really bugging me :)

looks like a handful are over the length limit now, let me know if you want me to fix this for you

@sigmavirus24
Copy link
Member Author

Black reformatted for me. I'll fix the others too

@sigmavirus24 sigmavirus24 force-pushed the fix-extend-default-ignore branch from 8fc745d to 4fe6f53 Compare April 15, 2021 18:23

Verified

This commit was signed with the committer’s verified signature.
sigmavirus24 Ian Stapleton Cordasco
Since Flake8 3.0 we've had the ability for plugins to use
`extend_default_ignore` to register codes they want disabled by default.
This, however, was a permanent disabling unfortunately. Our code didn't
have a way of understanding that this new set of `ignore` codes was
actually the 'default' set for that run. Much like the
extended_select_list, we now attach extended_ignore_list to be able to
confidently determine if the ignore we get in the DecisionEngine is
actually the Default Ignore list and what plugins what us to ignore by
default.

Refs PyCQA/pep8-naming#157
@sigmavirus24 sigmavirus24 force-pushed the fix-extend-default-ignore branch from 7c89ee3 to 2bb0308 Compare April 15, 2021 18:26
@sigmavirus24
Copy link
Member Author

I'm not sure what your release plans are @asottile so I'll let you merge this

@asottile asottile merged commit 3614150 into master Apr 15, 2021
@asottile asottile deleted the fix-extend-default-ignore branch April 15, 2021 22:18
@asottile
Copy link
Member

I'm not planning to release for a while, but if this is important to you I can backport it to 3.9.x -- let me know!

@sigmavirus24
Copy link
Member Author

If you have docs around doing the backport I can also do it. I don't want to keep @ecolell hanging on that PR for too long. (Also knowing full well that pep8-naming will likely need a >=3.9.x for whatever value of x it ends up being.

@asottile asottile modified the milestones: 3.9.1, 4.0.0 Apr 16, 2021
@asottile
Copy link
Member

alrighty! released this as 3.9.1

I decided to run the release myself since there were significant conflicts

@sigmavirus24
Copy link
Member Author

Thank you!

orviz pushed a commit to EOSC-synergy/mypipline.sqaaas that referenced this pull request Jan 30, 2023

Unverified

The signing certificate or its chain could not be verified.
Reason: PyCQA/flake8#1317
Signed-off-by: Fredo Erxleben <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants