As written, consistency suggests thatclass MyEG(BaseExceptionGroup, ValueError): should be unable to wrap anything butValueErrors!

That may in fact be the intention, and it wouldn't break thetrio.MultiError-as-BaseExceptionGroup deprecation pathway, but it's not the implementation and the tests don't distinguish these cases.

Otherwise, I think we'd want to document the behavior which is that "any subclass ofExceptionGroup can only wrap instances ofException, likeExceptionGroup itself.",and thereforeclass MyEG(BaseExceptionGroup, ValueError): would be able to containBaseExceptions 🤔

As written, this suggests that class MyEG(BaseExceptionGroup, ValueError): should be unable to wrap anything but ValueErrors!

Does it? In the doc the Exception becomes a hyperlink.

But feel free to make a PR with better wording.

I expect some users to read that as "if a subclass of BaseExceptionGroup is also a subclass of X, it can only wrap instances of X"; I'll open a PR to rephrase as "if it's also a subclass of Exception, it can't wrap BaseExceptions".

But then we're still treatingException as particularly special for subclasses, which feels a bit strange.

Zac, I'm confused why you think the sentence as written could be interpreted that way. It saysException twice. In this context that is very clearly a reference to the specific built-in class namedException (it even links there), not a "free variable" that must refer to the same class in both places.

Regardless, even if we clear that up, it feels like it would be expensive to inspect the class hierarchy to find other subclasses ofBaseException and try to constrain the arguments to inherit from those. And that's definitely not what the PEP intended. We want the common case (where you're using one of the two built-in EG classes) to be foolproof, and other casespossible.

Apologies for the confusion, that's on me 😞

I do think the behavior in this PR is good, and I'll open a PR with some additional tests and maybe docs to distinguish it from the case that I was wondering about. Thanks again to both of you for everything.