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

Remove detection of strings in B018 #209

Merged
merged 1 commit into from Nov 29, 2021
Merged

Conversation

kasium
Copy link
Contributor

@kasium kasium commented Nov 29, 2021

Stops false positive for #208 issue - We need to evaluate if we can be smarter and re-add this detection in future releases.

Copy link
Collaborator

@cooperlees cooperlees left a comment

Choose a reason for hiding this comment

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

Thanks for the workaround. I'd like to release possibly today a less noisy version for people until we workout if we can re-enable strings and avoid this edge case.

I feel we could add an example string to the unittests to ensure we're actually now ignoring it. And then use it for the upcoming true fix (if we can).

tests/b018_classes.py Show resolved Hide resolved
@cooperlees cooperlees merged commit 225f4e6 into PyCQA:master Nov 29, 2021
@kasium kasium deleted the issue-208-4 branch November 29, 2021 19:47
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