catch now raises typeerror on async handler

[jakkdl]

@Zac-HD
Fixes #66

I'm not entirely sure about the error message - which ones of exc, excgroup, matched and/or exc_types should be printed, and should we print the str, repr, or __name__.

Currently it looks like:

E   TypeError: Error trying to handle ExceptionGroup('', [TypeError('second argument (exceptions) must be a sequence')]) with <function test_async_handler.<locals>.handler at 0x7f319f598b80>. Exception handler must be a sync function

which certainly isn't the prettiest.

[coveralls]

Pull Request Test Coverage Report for Build 5533655265

• 6 of 6 (100.0%) changed or added relevant lines in 1 file are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+2.5%) to 98.641%

---

Totals
Change from base Build 5513148018:	2.5%
Covered Lines:	508
Relevant Lines:	515

---

💛 - Coveralls

[jakkdl]

Hm, I'm utterly failing to suppress the RuntimeWarning about handler not being awaited in the test when at the same checking for pytest.raises. I've tried pretty much all variants in https://docs.pytest.org/en/7.1.x/how-to/capture-warnings.html and putting the guards at different places in the test case but it seems like pytest.raises overrides warnings.catch_warnings() / pytest.warns() / recwarn

[jakkdl]

sorry for the force-pushing, I pushed ignoring the RuntimeError just before I saw your change suggestion which fixed that, so I rebased away my commit.

[agronholm]

Thanks!

[jakkdl]

My pleasure! 🚀