You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 6.54.0, hypothesis uses exception notes (PEP 678) to show falsifying examples underneath the raised exception. With python < 3.11, this is done using a custom exception hook provided by exceptiongroup, a backport of PEP 654. The problem is that trio also uses a custom excepthook to manage multi-errors. In practice, this leads to the falsifying example not being displayed depending on the import order. Even worse, simply having pytest-trio installed causes the falsifying examples to disappear. Consider the following test:
Thanks I edited the description of #2213 so that it closes this issue when merged. A Trio release will quickly follow anyway, as it's a long awaited feature and Python 3.11 will be release next month.
Since version 6.54.0, hypothesis uses exception notes (PEP 678) to show falsifying examples underneath the raised exception. With python < 3.11, this is done using a custom exception hook provided by exceptiongroup, a backport of PEP 654. The problem is that trio also uses a custom excepthook to manage multi-errors. In practice, this leads to the falsifying example not being displayed depending on the import order. Even worse, simply having
pytest-trio
installed causes the falsifying examples to disappear. Consider the following test:Without
pytest-trio
installed you would get:And with
pytest-trio
installed:The text was updated successfully, but these errors were encountered: