Issue

I want to propose to change how TRY003 works with some of the builtin exceptions. While I like how the rule applies to custom exceptions and "base" Exception, I think it's incorrect in the case of errors like TypeError and ValueError. It's a common pattern and is widely recommended to use those exceptions when type or value don't match the expectations.
Here you suggest to define a subclass of Exception, but not only defining a separate exception for every case is redundant and would bloat the code, I'm pretty sure using ValueError would more correct.

You already ignore NotImplementedError, which was a decision in the right direction! It doesn't make sense to subclass it every time. I think the same applies for at least ValueError and TypeError.

Solution

Currently you have such code to ignore NotImplementedError:

Info

Related issues: #2246 #6528

Sample code:

def compute(a: int, b: int) -> int:
     if a <= 0:
         raise ValueError("a must be > 0")  # Ruff: Avoid specifying long messages outside the exception class [TRY003]
     if not b:
         raise ValueError("b must be != 0")  # Ruff: Avoid specifying long messages outside the exception class [TRY003]
     return a + b

ruff command: ruff check --no-fix

ruff version: 0.7.4

ruff settings:

[tool.ruff.lint]
select = ["TRY003"]