{* ../../docs_src/handling_errors/tutorial001_py310.py hl[1] *}

### Lever une `HTTPException` dans votre code { #raise-an-httpexception-in-your-code }

`HTTPException` est une exception Python normale avec des données supplémentaires pertinentes pour les API.

Comme il s'agit d'une exception Python, vous ne la `return` pas, vous la `raise`.

Request gereksinimleri (header'lar gibi) veya başka alt dependency'ler tanımlayabilirler:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

### Exception Fırlatmak { #raise-exceptions }

Bu dependency'ler, normal dependency'lerde olduğu gibi `raise` ile exception fırlatabilir:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[10,15] *}

### Return Değerleri { #return-values }

Они могут объявлять требования к запросу (например HTTP-заголовки) или другие подзависимости:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

### Вызов исключений { #raise-exceptions }

Зависимости из dependencies могут вызывать исключения с помощью `raise`, как и обычные зависимости:

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[10,15] *}

### Возвращаемые значения { #return-values }

        message += f"\nField: {error['loc']}, Error: {error['msg']}"
    return PlainTextResponse(message, status_code=400)


@app.get("/items/{item_id}")
async def read_item(item_id: int):
    if item_id == 3:
        raise HTTPException(status_code=418, detail="Nope! I don't like 3.")

Elles peuvent déclarer des exigences pour la requête (comme des en-têtes) ou d'autres sous-dépendances :

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[8,13] *}

### Lever des exceptions { #raise-exceptions }

Ces dépendances peuvent `raise` des exceptions, comme des dépendances normales :

{* ../../docs_src/dependencies/tutorial006_an_py310.py hl[10,15] *}

### Gérer les valeurs de retour { #return-values }

### Siempre `raise` en Dependencias con `yield` y `except` { #always-raise-in-dependencies-with-yield-and-except }

Si capturas una excepción en una dependencia con `yield`, a menos que estés lanzando otra `HTTPException` o similar, **deberías volver a lanzar la excepción original**.

Puedes volver a lanzar la misma excepción usando `raise`:

// execution of newly issued ops.
//
// Note that outputs of discarded ops remain in a corrupt state and should not
// be used for future calls.
// TODO(agarwal): mark the affected handles and raise errors if they are used.
TF_CAPI_EXPORT extern void TFE_ExecutorClearError(TFE_Executor*);

// Sets a custom Executor for the current thread. All nodes created by this

### 在代码中触发 `HTTPException` { #raise-an-httpexception-in-your-code }

`HTTPException` 是额外包含了和 API 有关数据的常规 Python 异常。

因为是 Python 异常，所以不能 `return`，只能 `raise`。

这也意味着，如果你在*路径操作函数*里调用的某个工具函数内部触发了 `HTTPException`，那么*路径操作函数*中后续的代码将不会继续执行，请求会立刻终止，并把 `HTTPException` 的 HTTP 错误发送给客户端。

在介绍依赖项与安全的章节中，你可以更直观地看到用 `raise` 异常代替 `return` 值的优势。

本例中，客户端用不存在的 `ID` 请求 `item` 时，触发状态码为 `404` 的异常：

FastAPI 0.110.0 öncesinde, `yield` kullanan bir dependency kullanır, sonra o dependency içinde `except` ile bir exception yakalar ve exception'ı tekrar raise etmezseniz; exception otomatik olarak herhangi bir exception handler'a veya internal server error handler'a raise/forward edilirdi.

### Sempre levante (`raise`) em Dependências com `yield` e `except` { #always-raise-in-dependencies-with-yield-and-except }

Se você capturar uma exceção em uma dependência com `yield`, a menos que você esteja levantando outra `HTTPException` ou coisa parecida, **você deve relançar a exceção original**.

Você pode relançar a mesma exceção utilizando `raise`: