```Python
contents = myfile.file.read()
```

/// note | Technische Details zu `async`

Wenn Sie die `async`-Methoden verwenden, führt **FastAPI** die Datei-Methoden in einem <abbr title="Mehrere unabhängige Kindprozesse">Threadpool</abbr> aus und erwartet sie.

///

/// note | Technische Details zu Starlette

///

Para evitar bloquear o loop de eventos, você pode simplesmente declarar a função de operação de rota com `def` normal em vez de `async def`. Assim, o FastAPI a executará em um worker de threadpool, evitando bloquear o loop principal.

{* ../../docs_src/stream_data/tutorial002_py310.py ln[30:34] hl[31] *}

/// tip | Dica

///

### Pfadoperation-Funktionen { #path-operation-functions }

Wenn Sie eine *Pfadoperation-Funktion* mit normalem `def` anstelle von `async def` deklarieren, wird sie in einem externen Threadpool ausgeführt, der dann `await`et wird, anstatt direkt aufgerufen zu werden (da dies den Server blockieren würde).

```Python
contents = myfile.file.read()
```

/// note | Detalles Técnicos de `async`

Cuando usas los métodos `async`, **FastAPI** ejecuta los métodos del archivo en un threadpool y los espera.

///

/// note | Detalles Técnicos de Starlette

```Python
contents = myfile.file.read()
```

/// note | `async` Teknik Detaylar

`async` method’ları kullandığınızda, **FastAPI** dosya method’larını bir threadpool içinde çalıştırır ve bunları await eder.

///

/// note | Starlette Teknik Detaylar

///

### Функції операції шляху { #path-operation-functions }

Коли ви оголошуєте функцію операції шляху зі звичайним `def` замість `async def`, вона виконується у зовнішньому пулі потоків (threadpool), який потім «очікується», замість прямого виклику (оскільки прямий виклик блокував би сервер).

    * Add optional `use_unbounded_threadpool` argument to `map`, to specify that the `map` should use an unbounded threadpool instead of the default pool that is based on the number of cores on the machine. This can improve throughput for map functions which perform IO or otherwise release the CPU.

 *   java .teamcity/scripts/CheckWrapper.java < commits.txt
 *
 * Reads commit SHAs from stdin (one per line), checks wrapper per commit.
 */
public class CheckWrapper {
    private static final ExecutorService THREAD_POOL = Executors.newCachedThreadPool();

    private static final Pattern ALLOWED_WRAPPER_VERSION =
        Pattern.compile("^[0-9.]+(-(rc|milestone|m)-[0-9]+)?$");

    // Keep the same extraction semantics as the old sed:

 *
 * If any "bad" merge commit is found, it will print the details and exit with non-zero code.
 */
public class CheckBadMerge {
    private static final ExecutorService THREAD_POOL = Executors.newCachedThreadPool();

    private static final List<String> MONITORED_PATHS = Collections.unmodifiableList(Arrays.asList(
        "subprojects/docs/src/docs/release/notes.md",

    private static final long serialVersionUID = 1L;

    /**
     * Resource type that caused the error
     */
    public enum ResourceType {
        FILE_HANDLE, CONNECTION, MEMORY, DISK_SPACE, QUOTA, LOCK, BUFFER, THREAD_POOL
    }

    private final ResourceType resourceType;
    private final long availableResources;
    private final long requestedResources;

    /**
     * Creates a resource exception
     *