Skip to content
New issue

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

Transition from CompositeError to builtin ExceptionGroup #814

Open
Zac-HD opened this issue Jun 30, 2023 · 1 comment
Open

Transition from CompositeError to builtin ExceptionGroup #814

Zac-HD opened this issue Jun 30, 2023 · 1 comment

Comments

@Zac-HD
Copy link

Zac-HD commented Jun 30, 2023

PEP-654 adds a new builtin ExceptionGroup type to Python, and except* syntax for cleanly handling multiple errors. The backport is already widely used, including by Pytest, Trio, Hypothesis, and many others. I'd love to see ipyparallel join in, so that all our users get interoperable tooling and - once they're on recent versions of Python - nice syntax too.

Logistically, this is a substantial lift, but following e.g. python-trio/trio#2213 will hopefully be a lot easier than doing the whole thing from scratch. You might even choose to wait a while for the ecosystem to mature, but I thought it was worth opening an issue now - if nothing else, it's relevant to any other proposed changes to CompositeError - and I'm confident that switching over will be the best way forward within the next few years.

@minrk
Copy link
Member

minrk commented Jul 3, 2023

I haven't had time to look deeply into it, but that sounds perfect! Not sure when I'll get to it, but it seems very sensible.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants