TST: Remove bare pytest.raises

[gdex1]

References #30999

Adds match argument to pytest.raises found in the following files. #30999 (comment)

ToDo:

• pandas/tests/arithmetic/test_numeric
• pandas/tests/arithmetic/test_object
• pandas/tests/arithmetic/test_timedelta64
• pandas/tests/arrays/interval/test_interval
• add whatsnew entry

[pep8speaks]

Hello @gdex1! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

There are currently no PEP 8 issues detected in this Pull Request. Cheers! 🍻

Comment last updated at 2020-01-21 15:20:05 UTC

[WillAyd]

Any reason for the TODO here instead of adding the message?

[gdex1]

@WillAyd . I was not sure what a good error message for this function would be. Does the error message added in my previous commit work?

[gdex1]

Could someone give me some direction on resolving the failed integration tests? I do not understand how changing a string to an f-string in my latest commit would cause the error:
Git checkout failed with exit code: 128.

[WillAyd]

I think GitHub CI was temporarily down; just restarted let's see

[WillAyd]

lgtm

[jreback]

thanks @gdex1

[gdex1]

@MomIsBestFriend . I've finished adding match arguments for pytest.raises calls in these files. Should I add an entry to the "whatsnew" file? Or will there be one added later related to the original issue you opened? Thanks.

[ShaharNaveh]

@gdex1 First, thank you for contributing:)

And the "what's new" is a file that's displayed to users who wants to learn what's changed.

the tests are for us to test the code, the external users do not use these tests and they also don't see these tests, so no you should not create a what's new file.

And there will be no new entry for the related issue :)

---

Side note:
Don't be afraid to do mistakes (that's how you learn).
I'm sure, if you open a PR (related to this issue) with a what's new entry, you'll receive feedback (and better one).

---

:)