We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
just needs to be stringified
The text was updated successfully, but these errors were encountered:
why it's important to test specific Exception messages/types :P
Sorry, something went wrong.
@jtratner should we start assembling something in the wiki like:
Exhibit A: PR #4956 A classic example of why ....
😃
maybe wiki entries on when to use each type of exceptions?
yeah, I think that's better. though the codebase is still riddled with Exception raising:
›› grin "raise.*Exception" | wc -l 262
Though many of them should actually just be AssertionErrors...
We started one a while ago, but then I realized that there were almost no places where it was justified to use a custom Exception type anyways, so I didn't bother with it. - https://github.com/pydata/pandas/wiki/Choosing-Exceptions-to-Raise
I updated it.
cpcloud
Successfully merging a pull request may close this issue.
just needs to be stringified
The text was updated successfully, but these errors were encountered: