FileResponse is catching a FileNotFoundError to raise a RuntimeError

[bcb]

Found this in FileResponse:

except FileNotFoundError:
    raise RuntimeError(f"File at path {self.path} does not exist.")

I feel this is catching one exception just to raise a less meaningful one. For my unit tests, I would prefer to expect the FileNotFoundError is raised.

[Kludex]

Closing for housekeeping. I don't think a change is necessary here.

[micky2be]

How can one catch a FileNotFoundError (404) correctly?

[toxadx]

Raising a RuntimeError in case of a FileNotFoundError is meaningless.
FileResponse should either leave file-related exceptions as they are, allowing them to be caught by ExceptionMiddleware, or raise custom exception classes.
Please reopen the issue.