Trio's MultiError is deprecated in favor of the builtin (or backport of) ExceptionGroup, so downstream code should be written or ported to the latter. That includes catching, raising, and use of methods - so I think just linting for any reference to trio.MultiError would be sufficient and easy to implement.
This lint is important because MultiError is still raised from Trio, in order to give downstream time to migrate, and so users quite naturally use the name mentioned in their tracebacks.
Trio's
MultiErroris deprecated in favor of the builtin (or backport of)ExceptionGroup, so downstream code should be written or ported to the latter. That includes catching, raising, and use of methods - so I think just linting for any reference totrio.MultiErrorwould be sufficient and easy to implement.This lint is important because
MultiErroris still raised from Trio, in order to give downstream time to migrate, and so users quite naturally use the name mentioned in their tracebacks.