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
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
1.2.0
3.12.3
============================= test session starts ============================== platform linux -- Python 3.12.3, pytest-8.1.1, pluggy-1.4.0 rootdir: /build/source configfile: pyproject.toml testpaths: tests collected 99 items tests/test_apport_monkeypatching.py s [ 1%] tests/test_catch.py ................. [ 18%] tests/test_catch_py311.py .......... [ 28%] tests/test_exceptions.py ..............................FF........... [ 71%] tests/test_formatting.py .......ss...ss..ss.s.s.s.s. [ 98%] tests/test_suppress.py . [100%] =================================== FAILURES =================================== _______________ DeepRecursionInSplitAndSubgroup.test_deep_split ________________ tests/test_exceptions.py:375: in test_deep_split with self.assertRaises(RecursionError): E AssertionError: RecursionError not raised ______________ DeepRecursionInSplitAndSubgroup.test_deep_subgroup ______________ tests/test_exceptions.py:380: in test_deep_subgroup with self.assertRaises(RecursionError): E AssertionError: RecursionError not raised
Presumably upgrading to Python 3.12.3 or later should reproduce this test failure.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Things to check first
I have searched the existing issues and didn't find my bug already reported there
I have checked that my bug is still present in the latest release
Exceptiongroup version
1.2.0
Python version
3.12.3
What happened?
How can we reproduce the bug?
Presumably upgrading to Python 3.12.3 or later should reproduce this test failure.
The text was updated successfully, but these errors were encountered: