Veja, por exemplo, a seção `### Quotes` em `docs/de/llm-prompt.md`.

////

## Citações em trechos de código { #quotes-in-code-snippets }

//// tab | Teste

`pip install "foo[bar]"`

Exemplos de literais de string em trechos de código: `"this"`, `'that'`.

Um exemplo difícil de literais de string em trechos de código: `f"I like {'oranges' if orange else "apples"}"`

### 后台任务与带 `yield` 的依赖项（技术细节） { #background-tasks-and-dependencies-with-yield-technical-details }

在 FastAPI 0.106.0 之前，`yield` 之后抛出异常是不可行的，因为带 `yield` 的依赖项中的退出代码会在响应发送之后才执行，此时[异常处理器](../tutorial/handling-errors.md#install-custom-exception-handlers)已经运行完毕。

之所以这样设计，主要是为了允许在后台任务中继续使用依赖项通过 `yield`“产出”的对象，因为退出代码会在后台任务完成之后才执行。

在 FastAPI 0.106.0 中，这一行为被修改，目的是避免在等待响应通过网络传输时一直占用资源。

/// tip | 提示

    private static final String NAME_PREFIX = "failureUrlTest_";
    private static final String API_PATH = "/api/admin/failureurl";

    private static String webConfigId;

    @BeforeAll
    protected static void initAll() {
        RestAssured.baseURI = getFessUrl();
        settingTestToken();

        // Create and execute a web crawler to generate failure URL logs
        createWebConfig();
        logger.info("WebConfig is created");

errors.failed_to_print_thread_dump=Failed to print a thread dump.
errors.file_is_not_supported={0} is not supported.
errors.plugin_file_is_not_found={0} is not found.
errors.failed_to_install_plugin=Failed to install {0}.
errors.failed_to_find_plugins=Could not find available plugins.
errors.failed_to_process_sso_request=Failed to process a request: {0}

errors.property_required={0} is required.

errors.failed_to_print_thread_dump=Failed to print a thread dump.
errors.file_is_not_supported={0} is not supported.
errors.plugin_file_is_not_found={0} is not found.
errors.failed_to_install_plugin=Failed to install {0}.
errors.failed_to_find_plugins=Could not find available plugins.
errors.failed_to_process_sso_request=Failed to process a request: {0}

errors.property_required={0} is required.

val Project.gradleInstallPath: Provider<String>
    get() = gradleProperty(GRADLE_INSTALL_PATH).orElse(
        provider<String> {
            throw RuntimeException("You can't install without setting the $GRADLE_INSTALL_PATH property.")
        }
    )


val Project.rerunAllTests: Provider<Boolean>
    get() = gradleProperty(RERUN_ALL_TESTS).map { true }.orElse(false)

/// info | 정보

업로드된 파일을 전달받기 위해 먼저 [`python-multipart`](https://github.com/Kludex/python-multipart)를 설치해야합니다.

[가상 환경](../virtual-environments.md)을 생성하고, 활성화한 다음, 예를 들어 다음과 같이 설치하세요:

```console
$ pip install python-multipart
```

업로드된 파일들은 "폼 데이터"의 형태로 전송되기 때문에 이 작업이 필요합니다.

///

## `File` 임포트 { #import-file }

`fastapi` 에서 `File` 과 `UploadFile` 을 임포트 합니다:

## 新增自訂標頭 { #add-custom-headers }

有些情況需要在 HTTP 錯誤回應中加入自訂標頭，例如某些安全性情境。

你大概不需要在程式碼中直接使用。

但若你在進階情境中需要，可以這樣加入自訂標頭：

{* ../../docs_src/handling_errors/tutorial002_py310.py hl[14] *}

## 安裝自訂例外處理器 { #install-custom-exception-handlers }

你可以使用 [Starlette 的相同例外工具](https://www.starlette.dev/exceptions/) 來加入自訂例外處理器。

假設你有一個自訂例外 `UnicornException`，你（或你使用的函式庫）可能會 `raise` 它。

而你想用 FastAPI 全域處理這個例外。

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

Si quieres capturar excepciones y crear un response personalizado en base a eso, crea un [Manejador de Excepciones Personalizado](../handling-errors.md#install-custom-exception-handlers).

## Dependencias con `yield` y `except` { #dependencies-with-yield-and-except }

///

{* ../../docs_src/dependencies/tutorial008b_an_py310.py hl[18:22,31] *}

If you want to catch exceptions and create a custom response based on that, create a [Custom Exception Handler](../handling-errors.md#install-custom-exception-handlers).

## Dependencies with `yield` and `except` { #dependencies-with-yield-and-except }