Skip to content

Split B001 into B029 for empty tuple exception handling#344

Merged
cooperlees merged 4 commits intoPyCQA:mainfrom
FozzieHi:except-empty-tuple
Feb 3, 2023
Merged

Split B001 into B029 for empty tuple exception handling#344
cooperlees merged 4 commits intoPyCQA:mainfrom
FozzieHi:except-empty-tuple

Conversation

@FozzieHi
Copy link
Copy Markdown
Contributor

@FozzieHi FozzieHi commented Feb 2, 2023

This splits the part of B001's lint which checked for using except with an empty tuple, and moves it into a new lint, B029. As suggested by the comments in #282. Closes #282.

Copy link
Copy Markdown
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.

LGTM - Thanks for digging though issues and just doing them! Legend.

Comment thread bugbear.py Outdated
Comment thread README.rst Outdated
@FozzieHi
Copy link
Copy Markdown
Contributor Author

FozzieHi commented Feb 3, 2023

Thanks! Changes look good to me.

@cooperlees cooperlees merged commit 315f4e7 into PyCQA:main Feb 3, 2023
@FozzieHi FozzieHi deleted the except-empty-tuple branch February 3, 2023 17:50
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.

Confusing B001 message when catching empty tuple

2 participants