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
For now, we're punting by pinning trio to <0.25.0 for our CI. Instead, we should update our testsuite to use the new RaisesGroup and other testing tools to properly handle the ExceptionGroup wrapping.
I don't think there are any hazards to trio-asyncio users, beyond the fact that open_loop() now adds ExceptionGroup layers, so this should be just a testsuite change.
The text was updated successfully, but these errors were encountered:
For now, we're punting by pinning trio to <0.25.0 for our CI. Instead, we should update our testsuite to use the new RaisesGroup and other testing tools to properly handle the ExceptionGroup wrapping.
I don't think there are any hazards to trio-asyncio users, beyond the fact that
open_loop()
now adds ExceptionGroup layers, so this should be just a testsuite change.The text was updated successfully, but these errors were encountered: