Ability to gracefully exit from a lifespan error

[madduck]

Hello, please consider the following code:

from contextlib import asynccontextmanager
import sys

import uvicorn
from starlette.applications import Starlette
from starlette.responses import JSONResponse
from starlette.routing import Route


@asynccontextmanager
async def lifespan(_):
    sys.exit(0)
    yield


app = Starlette(
    lifespan=lifespan,
)

if __name__ == "__main__":
    config = uvicorn.Config(app)
    server = uvicorn.Server(config)
    server.run()

This will yield:

INFO:     Started server process [1829338]
INFO:     Waiting for application startup.
ERROR:    Traceback (most recent call last):
  File "/home/madduck/.tmp/2025-07-12-124819-starlette/.direnv/python-3.13.3/lib/python3.13/site-packages/starlette/routing.py", line 732, in lifespan
    async with self.lifespan_context(app) as maybe_state:
               ~~~~~~~~~~~~~~~~~~~~~^^^^^
  File "/usr/lib/python3.13/contextlib.py", line 214, in __aenter__
    return await anext(self.gen)
           ^^^^^^^^^^^^^^^^^^^^^
  File "/home/madduck/.tmp/2025-07-12-124819-starlette/test.py", line 16, in lifespan
    sys.exit(0)
    ~~~~~~~~^^^
SystemExit: 0

ERROR:    Application startup failed. Exiting.

This is misleading. SystemExit(0) is not an error, and the traceback is confusing.

Would it be possible to provide special handling for SystemExit or maybe another exception hierarchy, such that it would be possible to bubble up from a lifespan event error all the way to the console?

Also see:

• Lifespan error hangs system #2611
• How to handle exceptions thrown during lifespan startup? uvicorn#2665
• How to handle exception thrown during lifespan startup? fastapi/fastapi#13878